Luke Warlow

There's a better way to conditionalise them than detecting Firefox. @supports not (::-webkit-scrollbar) { } should do the trick (not checked exact syntax) in a more future proof way.

Are you able to close this issue as it's not a probably with the compat data, I've raised a separate content issue to make a more prominent note on the...

I'll go through these comments and address them later today.

LGTM other than that suggestion. Apologies I didn't find time to get back to this.

After https://github.com/mdn/browser-compat-data/pull/22866 is merged all of the compat data entries will be set up for any pages added for the various new APIs mentioned. https://github.com/mdn/content/pull/33141 - seeks to remove the...

Btw getHTML has been merged into the spec: https://html.spec.whatwg.org/multipage/dynamic-markup-insertion.html#html-serialization-methods and has an intent to ship in Chromium

This issue should be reopened it's not fully addressed yet and nor will it be when my second PR is merged.

A release note as well as an experimental features entry, for getHTML would be useful. https://github.com/mdn/content/pull/33492 could also do with a review on this one. The pages aren't exhaustive but...

`setHTML` is really tricky because the version that is documented *is* deprecated. I strongly believe removing the docs would be the most useful approach for developers. But policies prevent that...

> For the setHTMLUnsafe is this just called "unsafe" in contrast to the safe version that will eventually exist (point 1) which does sanitising? And again, we need this because...