It turns out that one the #performance issues I discovered some days ago in #GNOME#Web (where resources are not freed when closing a browser window) was caused by… a speed optimization previously made in the #Epiphany#opensource#Linux#browser … nearly 20 years ago 👀
Ok, so all upstream #webkit changes are merged in the @haiku development branch on my machine. I was a few month late in doing this (as I tried to spend time on getting WebKit2 to work, without much success so far).
There were some problems because WebKitLegacy for Windows was deprecated and with it went the support for cURL in WebKitLegacy. I reverted a few commits and it's building, but now it's not loading any pages. I'll try to fix that tomorrow...
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:
@rml I just listened to this the other day, very exciting! We will soon be able to do #FullStack development using #GuileScheme as the only language for the whole application!
I 100% agree with what @cwebber said about WebAssembly realizing the dream of Java's write-once-run-everywhere ethos. WebAssembly is the JavaVM done properly, with real support from the whole software development community at large.
A bit off topic, but I hope someday someone comes up with a fully #GPL#WebAssembly app platform that replaces #WebKit with something a fraction of it's size which runs on all the major operating systems. That is a tall order, yes, but not as hard as coming up with a whole new #WebBrowser engine. And it could replace both Node.js and the Java JRE.
Impressed that a #wikipedia editor who is on #mastodon has already updated the #webkit page today to reflect the correct information for @lisamelton 👍 Community sourced data for the win.
Just got my anniversary 100th pull request merged into #webkit ! One year ago I couldn't even imagine that!
Thank you, @igalia for believing in me and giving me the opportunity to work on such an important open-source project full-time! Life is great!
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/
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.
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!).
Please remember that this browser is not even in alpha, it's in pre-alpha. And does not have all the features it'll have (If I even get around to it, never know, I could get burnt out =P)
Yeah, I want to avoid Blink whenever possible. I only use it occasionally in Qutebrowser. There are similar browsers like luakit and vimb that use the much preferable #Webkit, but they aren't as nice to use.
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.
While I agree with the @fsf warning about the emblematic value of the decision by #Google to pull support for #JpegXL from #Chrome, their article <https://u.fsf.org/3z8> is as empty as could be, especially considering that #GNU#IceCat doesn't support JPEG XL either (being based on a #Firefox branch that doesn't build #JXL support in.) You want to show that #FLOSS can do without? Do it by actually supporting what you complain Google is failing to.
For #Firefox and its forks, this means enabling it out of the box for main builds. For #Blink-based browsers (@Vivaldi are you listening?), this means rolling back Google's patch to remove it, and help maintain it with community effort. Ditto for #WebKit. The #openWeb needs something like what the #DocumentFoundation did for the office productivity suites and formats.
Apple Issues Urgent Patch for Zero-Day Flaw Targeting iOS, iPadOS, macOS, and Safari (thehackernews.com)
Apple just released critical updates to combat an actively exploited zero-day flaw. Update to iOS 16.5.1 (a), iPadOS 16.5.1 (a), macOS Ventura 13.
New WebKit Features in Safari 17 beta (webkit.org)
Web Apps, 3D content, JPEG XL, and more.