Calling all web developers! Browsers are all meeting up next week (https://www.w3.org/events/tpac/2025/tpac-2025/). I want your voice to be heard! Tell me your biggest problems, and tell me what you want to see from the platform. What problems are tough to solve, but could be easier?
Discussion
Loading...
Post
@keithamus I'd like to see smaller browsers being included in decision making (Dillo, Lynx, Ladybird, etc).
I think that would bring some balance to the decision making process.
Given the resurgence of RSS, it might be nice to see some browser progress in that area.
Sadly, my dreams of background MIDI have been crushed. I'd settle for a single and consistent way to do high resolution favicons though!
@Edent @keithamus I don't think the W3C is interested in making a simpler subset of web specifications so they are aproachable by independent browser developers.
@Edent On your 1st point, to some degree this is "up to them". For e.g. Ladybird contribute a lot to WHATWG & CSS WG, and they're very welcome.
What looks like progress for RSS?
As for high res favicons, svg favicons are well supported, no? Or do you need raster?
(This isn't a rebuttal to your words, just trying to dig further)
@keithamus This one has various proposals or explains, but never seem to get any traction/progress:
<include src="./header.html" />
I want to build my HTML pages from HTML fragments without needing JS or a build pipeline. Seems like it would be so easy and so popular, both assumptions (real or imagined) that likely have made it harder to land (real or imagined) for the number of cooks it brings to the kitchen...
I think we do a okay job of assessing which newly designed features to prioritise (if you haven't already, check out https://interop-rank.jakearchibald.com/).
What I'm interested in is the problems _without_ proposed solutions. What are you working on where you just can't find even a proposal for?
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled