Position-area: Clear and explicit or short and sweet? - WebKit:
https://webkit.org/blog/17417/position-area-clear-and-explicit-or-short-and-sweet/
Post
Position-area: Clear and explicit or short and sweet? - WebKit:
https://webkit.org/blog/17417/position-area-clear-and-explicit-or-short-and-sweet/
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)
@rl_dane From the perspective of an implementer... I'd say that in the 2020s the W3C has gotten back to writing some superb specs! After some dubious trends in the 2010s.
The browser ecosystem isn't very healthy still...
A space for Bonfire maintainers and contributors to communicate