- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Apr 2018 09:24:07 +0000
- To: public-houdini-archive@w3.org
> It'll be exposing the inconsistencies in more places... Freshly exposing a previously-hidden inconsistency is a problem. Merely adding another place that exposes a previously-exposed one is fine; the inconsistency still needs to be fixed, but this adds no new problems. (And the base url used has a *very* large effect on URLs.) In general, this spec isn't trying to fix problems in core CSS, it's just providing a new way to inspect and manipulate CSS values. > And exposing "original url" doesn't seem super useful if it includes values that cannot even be parsed as a URL. Why would we do that? It lets you, if desired, exactly reproduce the string-OM behavior of moving a url value between stylesheets; you just have to construct a fresh CSSURLValue from the original url and new base url. I'm not of the opinion that this is particularly useful, but some in the WG wanted it, and it's not a problem to add it; we're just exposing information that's already obtainable via the string-OM. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/716#issuecomment-380033773 using your GitHub account
Received on Tuesday, 10 April 2018 09:24:12 UTC