<div dir="ltr"><div>Thanks for the answer, it looks like the version built for ArchLinux is missing some flag then. I'll try to figure out what's going on there.</div><div><br></div><div>However ...</div><div><br></div>> <span style="font-size:12.8px">Our team does not usually prioritize web-facing features </span><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">I wonder </span><span style="font-size:12.8px">then, </span><span style="font-size:12.8px">how's Gnome Web (Epiphany) trying to be the default Desktop/platform browser ?</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Beside that:</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">> </span><span style="font-size:12.8px">this webpage is what tech reviewers use to judge the quality </span><span style="font-size:12.8px">of web browsers</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">That page simply uses features detection, what every Web developer in this world would use instead of excluding through UA sniffing anythign that's not Chrome.</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">If CustomElementsRegistry is in there and customElements.define works I don't see why WebKitGTK would fail.</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">I know the author of that page though, and I'm both a Web/NodeJS developer and Web/NodeJS Polyfills author myself so I can counter verify what's going on.</span></div><div><span style="font-size:12.8px"><br></span></div><div><br></div><div><span style="font-size:12.8px">Last question, if I might:</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">> </span><span style="font-size:12.8px">Our team does not usually prioritize web-facing features</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">a Web engine that doesn't prioritize web-facing features sounds quite an "unsound" statement.</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">What's the official WebKitGTK focus/priority then?</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Thank You!</span></div><div><span style="font-size:12.8px"><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 3, 2017 at 9:45 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 Mon, 2017-04-03 at 19:18 +0100, Andrea Giammarchi wrote:<br>
> Dear All,<br>
> I've just played a bit around with WebKit2GTK 2.16 for ArchLinux,<br>
> out of Gnome-Unstable repository.<br>
><br>
> The <a href="http://html5test.com/" rel="noreferrer" target="_blank">http://html5test.com/</a> score is like 8 points more, still under<br>
> 400 out of 555.<br>
><br>
> Moreover, Custom Elements, as well as ES2015 script type=module are<br>
> not supported.<br>
><br>
> Am I missing flags during my initialization or nothing recent<br>
> actually went into this version?<br>
><br>
> Fetch is not there neither.<br>
><br>
> Mind explaining what's going on?<br>
><br>
> Thank You!<br>
<br>
</span>Custom elements works for me:<br>
<br>
<a href="https://webkit.org/wp-content/uploads/custom-element-demo.html" rel="noreferrer" target="_blank">https://webkit.org/wp-content/<wbr>uploads/custom-element-demo.<wbr>html</a><br>
<br>
The progress bar does nothing in 2.14 but works fine in 2.16. I see<br>
<a href="http://html5test.com" rel="noreferrer" target="_blank">html5test.com</a> scores it as unsupported. I'm curious why. For better or<br>
for worse, this webpage is what tech reviewers use to judge the quality<br>
of web browsers, and we're missing four points for custom elements.<br>
<br>
I dunno about ES6 modules, but I thought that should be working too.<br>
<br>
<a href="http://html5test.com" rel="noreferrer" target="_blank">html5test.com</a> says Fetch is working.<br>
<br>
Our team does not usually prioritize web-facing features except when<br>
somebody is paying us to do so (CSS grid layout), so I'm not at all<br>
familiar with any of the above. Maybe somebody else knows. For an<br>
overview of what we've been working on, see:<br>
<br>
<a href="http://blogs.igalia.com/carlosgc/2017/03/20/webkitgtk-2-16/" rel="noreferrer" target="_blank">http://blogs.igalia.com/<wbr>carlosgc/2017/03/20/webkitgtk-<wbr>2-16/</a><br>
<span class="HOEnZb"><font color="#888888"><br>
Michael<br>
</font></span></blockquote></div><br></div>