Why Google Sheets API Writes Don't Trigger onEdit or onChange Events

·2 views

A common source of confusion for Google Apps Script developers is that writing data to a spreadsheet via the Sheets API does not fire onEdit or onChange event triggers, as these only activate on direct user interactions. The distinction matters because script executions and external API requests are treated separately from user-driven edits by Google's trigger system. Developers can verify this behavior using a test setup involving a bound Apps Script project with installed triggers for edits, changes, and form submissions. Running a script write and an API values.update call in controlled conditions will show that neither produces a trigger execution, unlike a manual cell edit. Understanding this separation is essential for correctly architecting automation workflows that rely on spreadsheet event handlers.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Developer builds browser-only MOV to MP4 converter that never uploads your file

A developer has released movconverter, an open-source TypeScript library that converts MOV files to MP4 entirely within the browser, with no server uploads or file size restrictions. The tool exploits the fact that MOV and MP4 share the same underlying file format ancestry, meaning iPhone and Mac footage — already encoded in compatible H.264/HEVC and AAC formats — can be converted by rewriting metadata rather than re-encoding media. For less common cases involving PCM audio or ProRes video, the library falls back to WebCodecs or lazily loaded WebAssembly for transcoding. A free web interface is available at movtomp4.net, where users can drop in a file and complete the conversion locally without leaving the browser tab. The library also performs a preflight check before conversion, informing users in advance whether their file will be processed losslessly in seconds or require a slower audio transcode.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds Product Form Library Drawing on Surveys from Superhuman, Intercom and Airbnb

A developer has launched the Product Form Library, a curated collection of ready-to-use product forms inspired by research from teams including Superhuman, Intercom, Airbnb, and Chromium. The library aims to replace generic templates with carefully ordered questions and proven follow-ups drawn from published surveys and guidance. Forms cover a range of use cases including user feedback, onboarding, bug reports, feature adoption, and AI products. One highlighted example adapts Superhuman's product-market fit survey, which asks users how they would feel if they could no longer access the product. The creator is seeking community input on gaps in the collection and welcomes further feedback.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Build Screen-Reader-Friendly NBA Live Score Pages Using ARIA

A developer guide published on DEV Community outlines how to make real-time NBA scoreboards accessible to screen-reader users. The core challenge is that live basketball data — scores, clocks, and game status — updates constantly, but announcing every change would overwhelm assistive technology users with noise. The guide recommends using WAI-ARIA live regions, particularly role=status elements with implicit polite behavior, to deliver compact, meaningful announcements only when significant events occur, such as a score change or period end. Clock ticks should remain navigable but not auto-announced, since per MDN guidelines, not every real-time update warrants interruption. The article uses NBA Live Today, a Philippines-focused sports data platform, as a practical example, arguing that accessibility should be built into the live-data architecture from the start rather than added as an afterthought.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Handle Keyboard Focus Traps in Modals for Web Accessibility

Web accessibility requires that all interactive elements, including modals, be fully navigable using only a keyboard, as many users with visual or physical disabilities rely on it. A keyboard trap occurs when focus enters a section of a page and cannot be moved out using keyboard controls alone. For modals specifically, intentionally trapping focus inside is correct behavior — Tab should cycle only through elements within the modal, and pressing Esc or a close button must return focus to the element that triggered it. Without a keyboard-accessible exit, the modal becomes a true trap, rendering parts of the page unusable until a reload. The native HTML dialog element, governed by WCAG Success Criterion 2.1.2, handles all of this automatically, eliminating the need for custom keyboard management code.

0 comments Read more at DEV Community