No, but the answer involves either using width:100% (or similar) and box-sizing:border-box, display:flex (as @mike_conley's answer does), or display:grid. Maybe other ways too...
Basically, because nobody has yet written a spec for how CSS works on form controls like input. They're somewhere in-between "non-replaced elements" and "replaced elements" (for which you'd get different behaviors for the above -- replaced elements would use intrinsic width).
Some of these good policies (test, trace, and central quarantine, which I agree we should do) seem possible in the US only once we have substantially more testing capacity than we appear to have today.
But all of those state flags are bad. (Watch ted.com/talks/roman_mars_why… on flag design!)
(IMO the only good state flags are New Mexico and Texas, although Texas's flag has the disadvantage of looking too much like many others.)
How about "require" in the sense of requiring it, but with a somewhat moderate fine to push the ecosystem in the right direction? (Maybe NZ$5 or 10 per un-updated user per month?)
"The research revealed a previously hidden spread of the virus that might have been detected if aggressive testing programs had been put in place."
...
"So far, [...] researchers have identified seven separate lineages of viruses that entered New York and began circulating."
It seems like it should work if they used (prefers-color-scheme) media queries inside of their SVG favicon.
I wouldn't be surprised if it doesn't work. In fact, I'd probably be surprised if it worked across browsers...
2/3
I appreciate that @github is changing the site's favicon in response to the system's light/dark color scheme (probably drafts.csswg.org/mediaquerie…). It's improved the UI for me (dark theme).
Though it looks like they're using JS to change the <link rel=icon> links.
1/3