- From: Ryosuke Niwa <notifications@github.com>
- Date: Tue, 13 Nov 2018 21:20:20 +0000 (UTC)
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 13 November 2018 21:21:17 UTC
> It absolutely is not limited to that; many of the early posts in this thread *explicitly* mention SVG CSS properties that take `url()`, and which are inherited. That is in the context of figuring out how `href` should work, not now `url` should work. > You can't push this issue off until later, as resolving it one way or another changes the fundamental behavior of commonly used properties. If Google's position is that (3) is a must have, then we have no consensus to proceed with your proposal. We (Apple's WebKit team) would then have to retract our support for the proposal until such time is reached that we have a complete solution for https://github.com/w3c/csswg-drafts/issues/1995 is proposed and a consensus is reached. As far as I can tell, that's unwarranted delay of resolving the issue that SVG use element doesn't work at all in shadow trees. I'd rather resolve that issue first before resolving other CSS global names pacing issue especially because that's a concern of CSS WG, not SVG or Web Platform WG. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/179#issuecomment-438441120
Received on Tuesday, 13 November 2018 21:21:17 UTC