- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 Jul 2020 17:35:18 +0000
- To: public-houdini-archive@w3.org
The CSS Working Group just discussed `using ObservableArray for the list-ish values in TypedOM`, and agreed to the following: * `RESOLVED: put the list in a "value" property, and add a forwarding for compat` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> Topic: using ObservableArray for the list-ish values in TypedOM<br> <TabAtkins> github: https://github.com/w3c/css-houdini-drafts/issues/948<br> <fremy> ScribeNick: fremy<br> <fremy> TabAtkins: I tried to get better support for array-like classes in WebIDL<br> <fremy> TabAtkins: because we have three things that expose lists, and could benefit from this<br> <fremy> TabAtkins: but given I made no progress, I ended up using the legacy "getter/indexer" of WebIDL<br> <fremy> TabAtkins: but sadly that means that it's not an array<br> <fremy> TabAtkins: and you cannot use forEach etc on them<br> <fremy> TabAtkins: you have to convert them to an array first<br> <TabAtkins> https://heycam.github.io/webidl/#idl-observable-array<br> <fremy> TabAtkins: but domenic fixed this for me<br> <fremy> TabAtkins: and we have the observable array type<br> <fremy> TabAtkins: for the javascript user, it looks like an array<br> <fremy> TabAtkins: but it still triggers callbacks that allow us to type check things<br> <fremy> TabAtkins: so I'd like to switch to that<br> <fremy> TabAtkins: unfortunately that would result in a breaking change<br> <fremy> TabAtkins: indeed, the value itself cannot be an array<br> <fremy> TabAtkins: because it has to subclass the CSSValue type<br> <fremy> TabAtkins: so we need to store the list in a "values" member<br> <AmeliaBR> q+<br> <fremy> TabAtkins: for the math-value types, it's easier because it's already a FrozenArray<br> <fremy> TabAtkins: so I can just switch it<br> <fremy> TabAtkins: any objection to do this change?<br> <fremy> AmeliaBR: so, if I understand, you now need to do "x.values[0]" instead of "x[0]"?<br> <fremy> TabAtkins: if I don't accomodate that by making a special behavor, yes<br> <fremy> AmeliaBR: could we then make a putforward?<br> <fremy> TabAtkins: yes, we definitely can<br> <fremy> q+<br> <fremy> TabAtkins: and we could do that by just updating the code to do that and lookup in the array<br> <fremy> AmeliaBR: browser support?<br> <fremy> TabAtkins: yes, typedom is shipped in chrome<br> <fremy> TabAtkins: because paint api<br> <fremy> AmeliaBR: I would not like to break demos<br> <fremy> TabAtkins: yes, let's make the accomodation, it's not worth breaking the demos<br> <fremy> AmeliaBR: (restates)<br> <fremy> TabAtkins: (yes)<br> <AmeliaBR> ack AmeliaBR<br> <Rossen___> ack AmeliaBR<br> <Rossen___> ack fremy<br> <fantasai> fremy: I'm entirely in favor<br> <fantasai> fremy: Always thought it was really weird that ? and ?? you couldn't index it<br> <fantasai> fremy: so much cleaner for the PAI<br> <fantasai> fremy: not only improvement that you get an array<br> <fantasai> fremy: definitely in favor<br> <fantasai> fremy: and ??? sounds like a no-brainer<br> <fremy> TabAtkins: ok<br> <bkardell_> s/PAI/API ?<br> <fremy> s/??/forwarding<br> <fremy> TabAtkins: any concern from implementers?<br> <fremy> TabAtkins: looks like no?<br> <astearns> s/???/forwarding<br> <fremy> TabAtkins: any objection to adopt the change in the issue, with forwarding kept in?<br> <fremy> RESOLVED: put the list in a "value" property, and add a forwarding for compat<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/948#issuecomment-667245477 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 31 July 2020 17:35:20 UTC