I don't think people appreciate the role that #OperaSoftware played in fostering the #OpenWeb and #IndieWeb during the first #browserWar (when the #OperaBrowser was still built on their proprietary #Presto engine), and a fortiori the role it had in their demise (when they switched to being “just another #WebKit/#Blink skin”), despite their browser never even reaching a 3% market share.
This is what Amazon Prime Video could have looked like on visionOS had they not restricted web playback on mobile Webkit.
Did all this work and then realized that Prime Video requires the Widevine plugin to be present which mobile safari does not support. Interestingly, Prime Video works on desktop Safari, and forcing the user agent on mobile Safari to be desktop Safari doesn’t work. ☹️
Do I have any #Apple/#Webkit or #HTML specialist here? I want to know how many <audio> tags one can have in one HTML page for Mac/iOS? They are all with preload = none so that we don't load them at the same time.
I'm generally not a big fan of #Apple (understatement of the century), but I've read about the next version of #Safari officially supporting #JpegXL and I'm really glad that this is happening. I'm looking forward to the associated changes to #WebKit making it into the engine as it is used by other #FLOSS browsers too —and hopefully this will finally push @Mozilla into enabling #jxl in mainline #Firefox OOTB.
1/
#Safari 17 changes the time stretching algorithm for audio/video from the terrible, deprecated lowQualityZeroLatency option to timeDomain (the default for apps since iOS 15). This now means that speech-based audio is much more pleasant to listen to when scaled up in a web app, and is something I've been looking for in #WebKit release notes for a while.
Upside of many big companies not providing native app support for #visionOS could be that #WebKit gains support for hover effects for SVG elements that are annotated with cursor: pointer. Some love for FB13310281 please. Just saying. ❤️
#Webkit needs more exposure to mainstream users, and needs to be accessible on #Linux.
Everyone forgets about it, yet it's a respectible browser engine to my knowledge, and nobody seems to use it besides Apple and some light weight Linux browsers. In this browser monoculture, I'm unsure of why it isn't more popular with the alternative browser developers and users.
Little reminder, that @kde ‘s #KHTML made its way through Apple, returned as #WebKit (#webkitgtk2) to the free desktops and still is a free and one of the most portable browser engines working well and serving as an alternative to #Gecko and #Blink.
Just ran it on a #PPC machine from 2004 yesterday.
Turns out that it is possible to load and play prime videos - thanks to some help from @khaost! I’ll be posting updates on this thread and hopefully if I run into any problems, someone will be kind and knowledgeable enough to help 🙏🏻😁.
I had one HTML5 drag and drop target that wasn't working in webkit browsers, but worked fine in Firefox. Took a little while to find this tidbit which explains the bug:
Three days ago, the 4th of November, would've been #KHTML 25 year anniversary. 🥳
Hoorrray!
WTF is KHTML?
Chances are you are kind of using it, because #WebKit and #Blink rendering engines are all forked from this open-source project originally intented for the browser of the KDE window environment.
This is all $AAPL's fault. Just like touch events; they went and built whatever worked for them and their garbage computers without consulting standards bodies, and we end up stuck with their shitty decisions.
Now that #WebKit, #Safari, Epiphany, etc. support this, I really hope we will see #Mozilla finish the job and flip the switch in #Firefox too, based on @krosylight's great work.
Hopefully then the #GoogleChrome team will acknowledge that yes, everybody in the #webdev industry wants this.
Constantly hunting the best tool for the job? It’s addictive. After a few months with Arc, I switched my default browser to Orion. Contrary to most other alternatives, the latter is based on #WebKit, but has native support for both Chrome and Firefox extensions built in. I’m already in love with its focus mode and lean appearance (which shouldn’t let you underestimate its feature set!).
Yo #linux#frontend#webdev people. It is a feasible option to use #gnome web to debug #safai bugs since they're both #webkit, right? If not, alternatives? Boosts welcome 😀