Comment #5 on issue 4334 by [email protected]: API: Should
CreateDataProperty overwrite accessors, or call them?
https://code.google.com/p/v8/issues/detail?id=4334
Yes, that's exactly what I want as well. In this particular case it's
likely because the innerWidth native setter does the wrong thing. Without
reading the code I'm presuming that there's an api accessor on the hidden
prototype chain that comes back and calls ForceSet which then masks it on
the actual object.
I'm not exactly sure what replaceable means. If it means that it breaks the
magicness of the property upon user-store, you'll want to make blink change
the internal state of the accessor to "user-specified" with a kind of
hidden property to store the user-specified value. (I'm not sure if it's
magic before user-store? Does innerWidth ever change? If not this is not an
issue anyway, we can just store the value there.) If later we need to make
this faster, we could support replaceable in the V8 API and do the work on
our side. That way blink doesn't need such a powerful API.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
