Thinking about dark/light mode pickers that have three options: Auto/Dark/Light. If the default is “Auto” — in what scenario might someone want to move away from Auto (which would visually be a noop to the same theme?) I’m using Light mode as my system preference, but it seems unlikely that I would swap from Auto (Light mode) to Light mode (not Auto) on a specific site
my privacy settings are that I’m fine with a geolocation API but it should only return a boolean that reveals whether or not I’m on planet earth
Today’s esoteric HTML element is <kbd> As in: please press <kbd>⌘</kbd> + <kbd>R</kbd> repeatedly when AWS causes your JavaScript to fail to load.
If you’re using CSS Nesting, make sure your minifier supports it! As I learned today, clean-css doesn’t support it yet:
is there really no low-level mechanism to intercept boolean primitive coercion in JavaScript? why can’t I extend `Boolean` to make `new MyBoolean(false)` be `falsy`? (I understand why it isn’t, but I want to make it so) > Note: Unlike other type conversions like string coercion or number coercion, boolean coercion does not attempt to convert objects to primitives by calling user methods.