[webkit-gtk] WebKitGTK+ VS Apple WebKit

[Andrea Giammarchi]

FYI the test apparently looks for V0 API which is based on
document.registerElement, hence the test fails.
I've filed a bug already, I'm sure they'll change that.
https://github.com/NielsLeenheer/html5test/issues/501

However, it's surprising the only thing missing thing in WebKitGTK to be a
fully ES2015 Standard compliant browser is the module export/import through
`<script type=module>` which is shipped already in Safari, but it's not
supported at all.

Is this something I could enable, maybe under experimental features, or not
in the engine at all?

Thank You!


On Tue, Apr 4, 2017 at 7:49 AM, Carlos Garcia Campos <cgarcia at igalia.com>
wrote:

> El lun, 03-04-2017 a las 18:43 -0500, Michael Catanzaro escribió:
> > Hi,
> >
> > I don't think Arch is missing build flags (in fact I strongly
> > encourage
> > using the defaults), I think it just needs more investigation. WebKit
> > does support CustomElementRegistry and customElements.define, so I'd
> > be
> > interested to know why it's not detected. It could be a WebKit bug,
> > or
> > it could be an html5test bug.
> >
> > On Mon, 2017-04-03 at 22:36 +0100, Andrea Giammarchi wrote:
> > > What's the official WebKitGTK focus/priority then?
> >
> > Fixing platform-specific bugs, improving overall robustness and
> > security, API improvements needed for desktop applications,
> > performance
> > in embedded and resource-constrained devices, WebRTC, and whatever
> > customers are paying us to work on. That's already a lot and we don't
> > have time for much more than that. We mostly leave web-facing feature
> > development to Apple because they are rich and we're not, and they're
> > doing a quite good job of it for us already IMO. When there are
> > platform-specific bits needed to make a feature work on Linux, we're
> > of
> > course interested in filling those in when we find time.
>
> I disagree with this, we have worked in web features in the past even
> if nobody paid us for it, just for our own interests or because the
> community asked for a certain feature. It's true that we don't have as
> many resources as Apple, but I don't think we just wait until they
> develop features for us. We don't need to be rich to contribute web
> features to WebKit.
>
> > Michael
> > _______________________________________________
> > webkit-gtk mailing list
> > webkit-gtk at lists.webkit.org
> > https://lists.webkit.org/mailman/listinfo/webkit-gtk
> >
> --
> Carlos Garcia Campos
> http://pgp.rediris.es:11371/pks/lookup?op=get&search=0xF3D322D0EC4582C3
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-gtk/attachments/20170404/38680cb8/attachment.html>