On 08/13/2018 12:25 PM, David Burns wrote:
Do we have sufficient tests
There are some tests, but as always, not enough. And there are areas which are
not spec'ed, like
dir-attribute handling on HTML elements with Shadow DOM and session history of
iframes which are in shadow DOM.
for this to guarantee webcompat and interop
with other browsers?CustomElements is easier, since it doesn't really change
much, just adds a way to add couple of callbacks to user defined elements.
And the behavior of those callbacks is somewhat easy to test.
Shadow DOM is trickier, since the specs aren't always quite up-to-date, or
leave things undefined.
Also, in general web components are relatively rarely used feature. Google has
been a big user, but it relies on
v0 implementations, meaning basically Blink, and uses polyfills with other
browsers.
So, there is definitely some risk breaking web sites, but there isn't too much
we can do other than trying to ship.
David
On 10 August 2018 at 15:49, smaug <sm...@welho.com> wrote:
I'm planning to keep Shadow DOM and Custom Elements turned on on
beta/release builds.
Target release is Firefox 63.
prefs are dom.webcomponents.customelements.enabled and
dom.webcomponents.shadowdom.enabled.
Custom elements has been enabled in Nightly since January and Shadow DOM
since late May.
Bugs:
https://bugzilla.mozilla.org/show_bug.cgi?id=1471947 (Shadow DOM)
https://bugzilla.mozilla.org/show_bug.cgi?id=1471948 (Custom Elements)
Even though the APIs are totally distinct, web pages expect either neither
be there or both, so they
need to ship together.
-Olli
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
