Tab Atkins Jr.

From the discussion, there were two significant pushbacks: 1. It might be useful to get the author/OS's original preference, even if the page is currently overriding that preference. 2. We...

> If you specify it means "my page only supports dark mode", so why do you even need to query the prefers-color-scheme media query in the first place? Can't you...

> Are you suggesting that JS matchMedia should work differently from CSS @media? i.e. JS matchMedia should continue to not be affected by and only CSS @media should be affected?...

Right, so those would be unaffected in your logistics.

Again, the question with any of these options is: what value are we providing to authors by leaving the `(prefers-color-scheme)` MQ broken by default? If we recommend authors always do...

Since all of the scrolling methods currently return `void`, they're very compatible with being upgraded into returning promises. I think this would be a fine feature, we just need implementor...

In an async function, the promise is rejected *only* when the function throws an error. All other cases result in a fulfilled promise. This pattern is generally followed by other...

I'm not too concerned, since that's a mistake in the first place and would be fixed by the author. Only places explicitly catching a thrown error and doing something meaningful...

My only concern is that if we wanted to allow more information to come in (the anchor's margin, or the anchor's right inset-area track, etc), it might not be as...

Hm, will look into this. (Sorry for missing the csswg-drafts version of the issue, @dholbert!)