[mediaqueries-4] Add note about min-/max- shortcoming vs proper range context#1083
Conversation
|
👍 to the note (tho given its length, I might reformat it into a |
d2dae8c to
b7d8f2f
Compare
b7d8f2f to
6abf748
Compare
oops, wasn't aware of that. just force-pushed an updated version of this PR. see what you think (wrapped the whole "For instance..." part into a |
|
Ooh, much better. Thanks! |
|
Is this supposed to work on any browser at the moment? |
|
@phistuck this isn't really the best place to ask about current browser support, but: currently, I believe range context is not supported by any (?) browsers. (additionally, once they support it, it would only be browsers/windows with a viewport smaller than 320px that show black, so on desktop this would only happen if you made the window small and/or zoomed in) |
Thank you! |
A follow-up to w3c#1083 that further expands the example to also include use of high-precision values (while we wait for browsers to support range context queries)
A follow-up to w3c#1083 that further expands the example to also include use of high-precision values (while we wait for browsers to support range context queries)
Closes #984