- From: Ryosuke Niwa <rniwa@apple.com>
- Date: Fri, 14 Feb 2014 19:25:37 -0800
- To: Boris Zbarsky <bzbarsky@MIT.EDU>
- Cc: Daniel Freedman <dfreedm@google.com>, Alex Russell <slightlyoff@google.com>, Elliott Sprehn <esprehn@chromium.org>, public-webapps <public-webapps@w3.org>
On Feb 14, 2014, at 7:16 PM, Boris Zbarsky <bzbarsky@MIT.EDU> wrote: > On 2/14/14 10:07 PM, Ryosuke Niwa wrote: >> We most vigorously object to making the CSS style resolver depend on JS >> DOM object properties. > > Ryosuke, I think you misunderstood the proposal. I'm pretty sure we all object to having the CSS style resolver depend on anything that involves JS properties. But it's not necessarily a problem to have it depends on internal node state that can be set via DOM APIs (e.g. it already depends on DOM attribute values and whatnot). > > So in implementation terms, an element would just have an internal boolean and setting "this.shadowRoot = undefined" or whatnot would set that boolean; the CSS machinery would read that boolean. That seems fairly workable to me; whether it's the sort of API we want is a separate issue that I have no opinion on. I see. So we’re going to have some special setter that magically updates node’s internal state when being set on “undefined”. That seems workable although I do agree that whether we want that sort of API is a separate issue. - R. Niwa
Received on Saturday, 15 February 2014 03:26:02 UTC