<div dir="ltr">Thanks, and to confirm I have 2.14 indeed, 2.15 is in AUR as unstable and not brebuilt.<div><br></div><div>I guess at this point I'll wait those two months :-)</div><div><br></div><div>Best Regards</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 25, 2017 at 3:54 PM, Michael Catanzaro <span dir="ltr"><<a href="mailto:mcatanzaro@igalia.com" target="_blank">mcatanzaro@igalia.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Wed, 2017-01-25 at 15:29 +0000, Andrea Giammarchi wrote:<br>
> If I might ask my last question: who makes the decision of "what<br>
> ships where"?<br>
<br>
</span>Whoever is working on the feature. If the people working on the feature<br>
decide to enable it in WebKitGTK+, then we'll get it. If not, we'll<br>
never get it until someone working on WebKitGTK+ decides they want it.<br>
Nobody keeps track of the delta in feature differences between the two<br>
ports. It's certainly something that would be desirable.<br>
<span class=""><br>
> As example, how comes Safari is shipping customElements but latest<br>
> WebKitGTK+ doesn't even have them behind a flag?<br>
<br>
</span>Ah, I figured this out: the problem is you are testing the stable<br>
branch. In 2.14 there is a hidden and unsupported<br>
-DENABLE_CUSTOM_ELEMENTS build flag you can try using, but it might not<br>
be enough because it'll probably be disabled at runtime as well, and we<br>
have no way to enumerate or enable runtime experimental features except<br>
for CSS grid. We have a WebKitGTK+ experimental features environment<br>
variable that only covers CSS grid and does not map to the actual<br>
experimental features we have in WebKit. We should probably remove this<br>
or fix it somehow because it's surely not working properly right now:<br>
it's not OK for it to only work for only one particular experimental<br>
feature.<br>
<br>
But if you're testing 2.15.3, custom elements should be enabled and<br>
working by default. At least I see a progress bar on the custom element<br>
demo page, exactly the same as in Chromium, whereas in 2.14 I don't see<br>
anything. So the problem is just different release cycles. We really do<br>
need the full six months to make sure we're releasing a stable product.<br>
2.16 will be released in two months.<br>
<span class="HOEnZb"><font color="#888888"><br>
Michael<br>
</font></span></blockquote></div><br></div>