[Webkit-unassigned] [Bug 249982] WebM unsupported in open source builds

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=249982

--- Comment #10 from Vladimir Prelovac <vprelovac at gmail.com> ---
Alexey I appreciate what you are trying to do. I hope you can appreciate my perspective too.

> The WebKit open source project cannot speak for Apple.

I would also prefer that there was indeed a clear separation between Apple and WebKit. However that is not the reality.

Today there is this article on WebKit's blog:

https://webkit.org/blog/13686/release-notes-for-safari-technology-preview-161/

Or this post few weeks ago:

https://webkit.org/blog/13591/webkit-features-in-safari-16-2/

If "WebKit open source project cannot speak for Apple", it is odd that this news is posted on WebKit site, and not on Apple's site.

Also today, WebKit twiiter account has tweeted this:

https://twitter.com/webkit/status/1613679412746256389

Why does not WebKit project speak for any other WebKit based browser (and there are over 20 WebKit-based browsers out there)?

Fact is that WebKit does it only for Apple's Safari, so we can agree that WebKit is indeed speaking for Apple. And I can understand why, Apple being the biggest contributor to the project.

So when community asks a question like why is a certain feature only allowed in Safari's version of WebKit, we are really looking for a simple and transparent answer. Maybe the support is experimental and Safari is the testing ground? 

It is not this particular feature that is point of my interest but I am concerned that there are many more features like this contributed to WebKit, but being limited to only Safari, and even worse without proving any explainations or guidance, and that would be concerning from a standpoint of WebKit's reputation and eco-system of developers willing to contribute to it.

If you would like the kind of independence for WebKit that we I think we both do, a bit of transparency from Apple developers reading this will go a long way.

Thank you.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230113/b31a58c2/attachment.htm>