Bug 104547 – Object.observe() not notified for changes to DOM properties

• Status: RESOLVED
• Resolution: INVALID
• Component: DOM

[Alex Russell]

Changes to DOM properties (not attributes) do not appear to trigger observers today. E.g.:

    Object.observe(window.navigator, console.log.bind(console));

Now go offline. 

We should observe that this logs a change to window.navigator.onLine, but currently does not.

This property, e.g., is specified as a readonly attribute and not a getter, and therefore should be observable:

    http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html#browser-state

[Oliver Hunt]

The general consensus is that all dom properties that are reflecting internal state will be represented as getters.  The bug here is not that the value is not observable, but that it is not explicitly specified as a getter.

[Alexey Proskuryakov]

Is there a bug tracking that?

[Oliver Hunt]

(In reply to comment #2)
> Is there a bug tracking that?

I believe so, but i'm at a loss to recall what it is -- maybe sam knows?

[Sam Weinig]

(In reply to comment #3)
> (In reply to comment #2)
> > Is there a bug tracking that?
> 
> I believe so, but i'm at a loss to recall what it is -- maybe sam knows?

https://bugs.webkit.org/show_bug.cgi?id=49739?

[Oliver Hunt]

(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #2)
> > > Is there a bug tracking that?
> > 
> > I believe so, but i'm at a loss to recall what it is -- maybe sam knows?
> 
> https://bugs.webkit.org/show_bug.cgi?id=49739?


That's the one