- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 14 May 2021 17:34:07 +0000
- To: public-houdini-archive@w3.org
(I assume you're objecting to the idea of the non-CSSColor classes having indexed properties, tho it's not entirely clear. If you're concerned about CSSColor having indexed properties as well, could you elaborate?) Plenty of classes with indexed properties also have some methods or attributes; that's not unusual. I'm already doing it in a few places in Typed OM, in fact. I think having some internal state being reflected in two different ways (indexed property and named attribute) is somewhat novel, but I doubt it's unheard of. (At bare minimum it's probably done for some legacy names.) It's not weird implementation-wise, tho; IDL attributes are always actually getter/setter pairs for the internal data, and having two things access the same internal info is fine. You already do this in Color.js, afaict, right? `color.hsl[0]` and `color.hsl.h` are both allowed. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/1037#issuecomment-841396236 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 14 May 2021 17:34:08 UTC