To elaborate on my hostility against WebKit: WebKit does nothing but get in my way whenever I work on literally any website.

When I rewrote nouveau's website in late 2023, it worked perfectly fine on Firefox (Gecko) and Chromium (Blink), but was broken on Epiphany/Safari (WebKit). The logo, which is an SVG, would not adapt to dark style, because, to this day, WebKit still does not support prefers-color-scheme in SVGs. So, as a workaround, instead of having one SVG file for both color schemes, we have one SVG file for light style, and one for dark style.

Another example: On my website, some elements are intentionally made to be unselectable using user-select: none;, such as the command-line decoration and the “Table of Contents” text, but on WebKit, these elements continue to be selectable because it does not properly support the user-select property. And no, using the vendor prefix is completely unacceptable, especially considering that it behaves differently.

Lastly, WebKit does not yet fully support the ::marker pseudo-element. This means, in my articles, numbered list items in the table of contents are completely wrong and don't represent the same numbers as headings.

Apple has consistently proved that they don't care about WebKit, because otherwise browsers like Safari and Epiphany would have worked as well as they do on Firefox and Chromium. There's absolutely no reason to force WebKit onto iOS and iPadOS if they're not even willing to invest in WebKit. Likewise, Apple employees working on WebKit should really stop calling themselves “WebKit evangelists” if their inferior engine regularly gets in developers’ way. So yes, WebKit sucks, and this is 100% on Apple. I don't care about being harsh. Apple is a multi-trillion dollar company, most of which came from exploiting people. The least they can do is invest in their projects.

For clarity, my hostility towards WebKit is purely targeted at Apple's lack of involvement with WebKit, not the browsers using it.

@jensimmons I would wish, that Apple contributes their WebRTC implementation for WebKit upstream to the Open Source project so that Gnome Web and other Free Software web browser would finally support WebRTC.

An employee of Cook/Jobs, @jensimmons, asks on a copylefted platform what she can do improve to #WebKit.

The answer is simple: Comply with the LGPLv2.1 —as your track record on that is abysmally poor. Participate with upstream projects rather than manipulating them so you can control them.

Employees of your company used to be forbidden from talking to FOSS communities. You've spent decades working against #copyleft. But you now follow Microsoft's plan to “embrace, extend, & extinguish” #FOSS.

Even though #ChromeOS is being devoured by Android, and $AAPL still anticompetitively hobbles #webkit, and #Firefox removed desktop PWAs, I still think the web is the future. The web is more capable than ever and everything that doesn't run on the web eventually will. It's just that this last mile of UI parity doesn't really matter. Typing URLs into a text box is fine. The web doesn't need to pretend to be something else!

Pour le scroll erratique : passer l'option "enable_smooth_scrolling" à 'true' à l'instance #Webkit semble améliorer les choses.

C'est pas aussi fluide que sous Firefox mais ça peut le faire.

@alcinnz @lapisdecor @dillo

If Mozilla folds tomorrow, I think the next possibilities are going to be (in no particular order)

• Servo - a former Mozilla project
• Ladybird - a completely new browser
• Gnome Web - a #Webkit-based browser

@passthejoe

I would beg you to reconsider. Not for Mozilla's sake or even Firefox's sake, but for the web's sake.

Having all web traffic come from #Blink-based browsers gives implicit ownership of the web to Google. We're already 76.5% there, but every percentage point from this point on will be increasingly bad.

I'm not saying that the alternatives to Blink are plenteous, or wonderful, because they're absolutely neither.

But to me, supporting a Blink hegemony by using a chromium-based, electron-based, or even qtwebengine-based browser is a total non-starter.

That's the primary reason why I stick with Firefox, despite Mozilla's innumerable gaffes.

Other than Gecko and Servo-based browsers, #Webkit-based browsers such as Gnome Web / Epiphany look decent. There's also #Ladybird which is a hopeful new from-scratch browser project.

@ajroach42
From what? #Firefox is not perfect, no human made thing is. But we can't have a #browser #monoculture, it is way too risky for several reason. That's also why I have a soft spot for all #webkit browsers also proprietary ones. #Chrome, #chromium and their derivates can't be the one web client we use. We need more engines for a healthy web ecosystem

@jensimmons @igalia @WebKitGTK @WPEWebKit it's just sad that few #WebKit browsers outside of #Chromium - modifications exist as #Google is actively enshuring neith #Chrome nor it's derivatves and siblings would ever see use by me...

Now who wants to help us land https://issues.chromium.org/issues/40062355 for #chromium can catch up to #webkit and support `:host(:has(...))` selectors too?

There's even web platform tests to support your work: https://wpt.fyi/results/css/css-scoping?label=master&label=experimental&aligned&q=host%20has-0

#mozilla don't think you can sneak away without expanding your coverage in both of these features as well!!