- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Feb 2018 20:45:26 +0000
- To: public-houdini-archive@w3.org
We'll still have to grapple with the fact that CSS's types don't have a nice subclass/superclass relationship; a <<url>> is a type of <<image>>, but it's also completely other, unrelated types. I suspect what we'll eventually want is to create a more generic `CSSURLValue` class as well, which can be used generally, and just define that it "matches" `<<image>>` as well as some other things. Then CSSURLImageValue and CSSURLValue, plus maybe some other specialized subclasses, can just spam the same language between them. We can look into abstracting it into a mixin later, but that's not necessary right now. So this'll still leave us with `.state` not being exposed, or the width/height/ratio (since they implicitly expose the state), yet, so that'll stay for level 2. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/716#issuecomment-368133468 using your GitHub account
Received on Friday, 23 February 2018 20:45:35 UTC