Re: [w3c/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179) from Sebastian Müller on 2018-10-12 (public-webapps-github@w3.org from October 2018)

From: Sebastian Müller <notifications@github.com>
Date: Fri, 12 Oct 2018 00:53:08 -0700
To: w3c/webcomponents <webcomponents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webcomponents/issues/179/429237987@github.com>

+1 for doing *anything* to make SVGs work - I have yet to see someone (a developer, not a spec writer) who prefers a standard conforming implementation where the standard says that it "must not work" over an implementation that actually works. I never thought I would say this, but I would even appreciate a new "workinghref" property that works!

-1 for not doing anything and waiting until either SVG or webcomponents or both are dead

That said - for us and our customers you did it: webcomponents are dead and we highly recommend against using them because SVG does not work.  Sorry for the rant, but "years" is just too long to wait for a working implementation. Let's just hope that Angular, React and Vue and whatever will come next will never switch to webcomponent technology.

-- 
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-429237987

Received on Friday, 12 October 2018 07:53:30 UTC