- From: Lea Verou <notifications@github.com>
- Date: Fri, 12 Dec 2025 22:35:33 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 13 December 2025 06:35:37 UTC
LeaVerou left a comment (whatwg/dom#1340) Yeah unfortunately observing property changes in general has been a longstanding NAK. I wonder if this may be easier to solve by scoping the use cases down. E.g. if most use cases are around form elements, we could have an event for this. ---- @annevk > > This is cumbersome to implement as not all browsers/platforms respond in the same way > > That seems like a bug that needs to be fixed. No reason to expect a new API is going to make this better. > > Also, there's no way to "just" make this work for arbitrary properties. That'd require patching every object. Making sure events fire consistently seems like a much better fix. Note that no event currently will pick up changes via JS setting a `.value` property directly. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/1340#issuecomment-3649043111 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/1340/3649043111@github.com>
Received on Saturday, 13 December 2025 06:35:37 UTC