#Chrome's deprecation of #XSLT is just the next step in the decade-long efforts by #Google to kill an open, independent web (reminder that I've collected some of that history here <https://wok.oblomov.eu/tecnologia/google-killing-open-web/>). The #WebKit developers at #Apple or the prone #Mozilla developers agreeing on this choice detracts nothing from the argument.

#openWeb #indieWeb

About to present our usual "Igalia and WebKit: Status Update and Plans" (2025 edition) talk in a couple of hours at the #WebKit Contributors Meeting. Lots of updates covering the work of several teams at @igalia, I hope it will be interesting and that we'll get some good feedback and questions!

About to present our usual "Igalia and WebKit: Status Update and Plans" (2025 edition) talk in a couple of hours at the #WebKit Contributors Meeting. Lots of updates covering the work of several teams at @igalia, I hope it will be interesting and that we'll get some good feedback and questions!

@jensimmons question.. why is the shorthand for text-decoration still not supported ? It's been in prefixed preview for 3.5 years now. Did people forget about it ?

https://developer.mozilla.org/en-US/docs/Web/CSS/text-decoration#browser_compatibility

Would be nice to see Safari catch up with the other browser vendors.

#safari #webkit

```
$ git clone --depth=1 --quiet https://github.com/mozilla-firefox/firefox.git
$ du -sh firefox
5.1G firefox
$
```
#firefox is also smaller than #WebKit.

```
$ git clone --depth=1 --quiet https://github.com/NetBSD/src.git NetBSD-src
$ du -sh NetBSD-src
4.3G NetBSD-src
$
```
#NetBSD is between #FreeBSD and #WebKit,

just to compare a web browser engine to a full operating system:
```
$ git clone --branch=release/14.3.0-p4 --depth=1 --quiet https://git.FreeBSD.org/src.git FreeBSD-src
$ du -sh FreeBSD-src
1.9G FreeBSD-src
$
```
#WebKit has nearly 4 times the source repository size compared to #FreeBSD.

```
$ git clone --depth=1 --quiet https://github.com/WebKit/WebKit.git
$ du -sh WebKit
7.4G WebKit
$
```
What the heck #WebKit?

@alcinnz

I don't have much of substance to add to that particular conversation, as my knowledge of HTML and web technologies peaked at about 2001, but I do wonder why #WebKit doesn't get more love from the Linux and FOSS community.

It seems so many browsers would rather be just another flavor of Chrom(e|ium) or another fork of Firefox than break with the norm.

I'm also sad that Qt abandoned WebKit altogether, which ironically was originally based on KHTML, which was built atop of Qt technologies, IIRC.

There may be very valid reasons for not wanting to base something on WebKit, I don't know. I just haven't heard much in the way of arguments against it that seemed cogent, other than a somewhat nebulous, "there's a reason why Google forked it."

(It may actually be my recollection of that statement that's nebulous, though)

@alcinnz

I don't have much of substance to add to that particular conversation, as my knowledge of HTML and web technologies peaked at about 2001, but I do wonder why #WebKit doesn't get more love from the Linux and FOSS community.

It seems so many browsers would rather be just another flavor of Chrom(e|ium) or another fork of Firefox than break with the norm.

I'm also sad that Qt abandoned WebKit altogether, which ironically was originally based on KHTML, which was built atop of Qt technologies, IIRC.

There may be very valid reasons for not wanting to base something on WebKit, I don't know. I just haven't heard much in the way of arguments against it that seemed cogent, other than a somewhat nebulous, "there's a reason why Google forked it."

(It may actually be my recollection of that statement that's nebulous, though)

Recently I got sufficiently annoyed at authoring posts in two places so that they were visible both here and on HaugenHus: Now – this is also in part because I prefer to write in Markdown which GoToSocial handles marvellously – that I decided to start looking at options. Of course there are many, but I chose to pursue an exclusively client-side solution with a static pageset to lighten the load on my little Raspberry Pi.

I landed on a solution built on HTMX + GoToSocial:RSS + XSLT which can be seen on HaugenHus: XSLT Test, but was horrified to find that after 26 years Firefox hasn’t managed to solve for HTML within an XML node. Of course it’s easy to get frustrated with a second-rate browser like Firefox 😁 – WebKit all the way baby! – but why bother when someone else has keep the flame war burning for 24 years Bug 98168 🤣. Of course with every ugly battle there are some heroes, and Scott Trenda was clearly one of these both offering a viable workaround and serving as a calm voice of reason.

So with a viable workaround to my XSLT woes, why haven’t I finished this little project? Well, there are two reasons: the first is that a workaround should never be allowed to become a permanent solution; and secondly, my WebKit enthusiasm may have been misplaced. It turns out that the fine folks over at Apple – @annevk – have expressed interest in killing my XSLT dreams 🥺.

With all of that said, what I found most interesting about this whole thing is that while I have been aware of XSLT for years, I unknowingly decided to play with it just as a storm appears to be brewing. Eventually I will get over my desire to minimize my dependence on JavaScript, but until then I’m sure there many other ways to solve this problem. I might just need to change the constraints.

(Maybe @gotosocial@superseriousbusiness.org would give us JSON Feed . . . feature request incoming after a bit more research 🤓.)

Additional Reading

XSLT Debate Leads to Bigger Questions of Web Governance

#Now #XSLT #Firefox #WebKit #GoToSocial #HTMX #RSS #JSONFeed

Recently I got sufficiently annoyed at authoring posts in two places so that they were visible both here and on HaugenHus: Now – this is also in part because I prefer to write in Markdown which GoToSocial handles marvellously – that I decided to start looking at options. Of course there are many, but I chose to pursue an exclusively client-side solution with a static pageset to lighten the load on my little Raspberry Pi.

I landed on a solution built on HTMX + GoToSocial:RSS + XSLT which can be seen on HaugenHus: XSLT Test, but was horrified to find that after 26 years Firefox hasn’t managed to solve for HTML within an XML node. Of course it’s easy to get frustrated with a second-rate browser like Firefox 😁 – WebKit all the way baby! – but why bother when someone else has keep the flame war burning for 24 years Bug 98168 🤣. Of course with every ugly battle there are some heroes, and Scott Trenda was clearly one of these both offering a viable workaround and serving as a calm voice of reason.

So with a viable workaround to my XSLT woes, why haven’t I finished this little project? Well, there are two reasons: the first is that a workaround should never be allowed to become a permanent solution; and secondly, my WebKit enthusiasm may have been misplaced. It turns out that the fine folks over at Apple – @annevk – have expressed interest in killing my XSLT dreams 🥺.

With all of that said, what I found most interesting about this whole thing is that while I have been aware of XSLT for years, I unknowingly decided to play with it just as a storm appears to be brewing. Eventually I will get over my desire to minimize my dependence on JavaScript, but until then I’m sure there many other ways to solve this problem. I might just need to change the constraints.

(Maybe @gotosocial@superseriousbusiness.org would give us JSON Feed . . . feature request incoming after a bit more research 🤓.)

Additional Reading

XSLT Debate Leads to Bigger Questions of Web Governance

#Now #XSLT #Firefox #WebKit #GoToSocial #HTMX #RSS #JSONFeed

TIL: Safari hides SVGs in Flexbox containers if they don't have an explicit width attribute. This seems like a bug to me.

svg {width: 100%} should fix the issue and hopefully not cause unexpectedly large images elsewhere🤞. #webdev #css #buildinpublic #webkit #opensource

https://github.com/pentacent/keila/commit/09254cb66319f996bfce8c3cfd251cfed76a7c1c

#Apple#Webkit#Webrtc#Gnome

While cleaning a few bits of logging code in #WebKit I found out a dollop of dead code 💀.
It's always a happy day when one gets to write a patch that only removes stuff → https://github.com/WebKit/WebKit/pull/47623

While cleaning a few bits of logging code in #WebKit I found out a dollop of dead code 💀.
It's always a happy day when one gets to write a patch that only removes stuff → https://github.com/WebKit/WebKit/pull/47623

I just realized that today is the 24th anniversary of when I started the #Safari and #WebKit projects at #Apple. 🤦‍♀️ Which just goes to show how much my life has moved on and changed since leaving the Fruit Company over a dozen years ago. 🤷‍♀️

Dog almighty, I am old AF. But let's keep that fact between ourselves, OK? 😂

It's also @kocienda's birthday. Which is why I remembered this at all. Happy birthday, Ken! 💖

I just realized that today is the 24th anniversary of when I started the #Safari and #WebKit projects at #Apple. 🤦‍♀️ Which just goes to show how much my life has moved on and changed since leaving the Fruit Company over a dozen years ago. 🤷‍♀️

Dog almighty, I am old AF. But let's keep that fact between ourselves, OK? 😂

It's also @kocienda's birthday. Which is why I remembered this at all. Happy birthday, Ken! 💖

Just arrived at Denver with other colleagues from @igalia to attend the #OSSummit North America, where I'll present my talk "Unlocking the Full Potential of @WPEWebKit To Build a Successful Embedded Product". More details in https://sched.co/1zflb

See you in just a couple of days!

#wpe #webkit