Luke Warlow

This was done a long time ago so closing out this issue

I'm not personally convinced (on first look) that this change would have a meaningful impact on migration? How common is it for a site to be setting an empty innerHtml...

It's also not entirely obvious to me that allowing empty strings would be expected to be considered safe by default either. As this could lead to page breakages with 0...

I would prefer to keep them in some form they're useful to make sure that Webkit and chromium match in their behaviour.

Are there any open questions with this functionality that needs any help?

As a heads up I'm currently prototyping adding a new user preference client hint `Sec-CH-Prefers-Reduced-Transparency` this as you can probably guess will reflect the `prefers-reduced-transparency` media feature (See #145 ).

https://html.spec.whatwg.org/multipage/nav-history-apis.html#navigation-api The navigation API has been merged into the HTML spec just as an fyi.

@hober as far as I know Background Sync and background fetch are separate APIs, just quite related.

If you're using Chromium (Chrome/Edge etc) this is expected behaviour, as of Chrome 121 the standard properties are supported and as always the standard CSS overrides the non-standard. I don't...

That's also expected. Chromium on Windows uses a different scrollbar style to Firefox. The test for whether it's an issue with the scrollbar properties is to remove them entirely and...