An update on Object.observe
andrea.giammarchi at gmail.com
Tue Nov 3 10:50:16 UTC 2015
Sure thing, meanwhile polymer or other libraries need to pollute getters
and setters and the rest of the web have been trying to polyfill it for at
least 6 years now *
The reason is not widely "abused" is that it never made it as standard and
as it is feels like an outdated spec. Proxy would give us that and much
more, unfortunately proxies do not play so well cross environment. For
while Object.prototype.watch always works, proxied GObjects fail to be used
like these were just GObjects.
That might be a specific env problem though, but having a way to watch
properties, specially in two ways bindings scenarios, is a very needed
As example, in DOMClass I'm replacing native getters/setters to be notified
about changes, it doesn't feel right even if it works.
All this is over-off-topic though, so I might just stop.
* just few examples since 2009
question in SO
yes, I've done that too
and recently https://gist.github.com/WebReflection/366dc38574dc526308b5
On Tue, Nov 3, 2015 at 2:11 AM, Boris Zbarsky <bzbarsky at mit.edu> wrote:
> On 11/2/15 4:55 PM, Andrea Giammarchi wrote:
>> I agree with Benoit and I think there is a reason
>> `Object.prototype.watch` is still in Firefox and won't go away any time
> As far as I know the only reason it's there and hasn't been removed is
> because it's used to implement debugger watchpoints . And the only
> reason it's web-exposed is because SpiderMonkey has not prioritized being
> able to expose APIs to privileged code but not the web (something that
> think should get fixed).
>  https://bugzilla.mozilla.org/show_bug.cgi?id=934669
> es-discuss mailing list
> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss