Personally, I wouldn't want to maintain a stylesheet with light-dark sprinkled everywhere.
I would much rather have the custom properties properly named (--button-primary, --text-secondary) and modify them in one place in :root, than trying to decipher pairs of light-dark throughout the stylesheet.
Posts by Damian
Also known as 'Buying'
Almost 10 years ago, there was a discussion about this on the W3C mailing list (even with possible implementation details), but it didn't trigger any action.
lists.w3.org/Archives/Pub...
A way to disable pre-multiplied color space in CSS, so that you have _full_ control over gradients.
Currently browsers try to read your mind when interpolating colors with alpha, and it's incompatible with some effects.
I wrote about it here: bsky.app/profile/oczk...
Got it! Can't wait to dig in. I also really appreciate Josh's support for regional pricing.
The mobile Signal client breaks words like "jak" into two lines.
@signal.org This is weird, but I suddenly can't write the words containing "j" and "k" without them getting a newline.
I'm writing "jak jak jak"
It displays as:
jak jak
jak
This only occurs on mobile. Desktop displays the message normally.
For reference, the first Cloud Alpha Wireless lasts over 300 hours, but doesn't have Bluetooth
AMD uses the word "AL" instead of "AI" on the product's official page. Perhaps they liked how the lowercase L looked?
Something felt off about this "AI" word there. Turns out it's not "AI". It's "Al"—or AL, if you capitalize it.
www.amd.com/en/products/...
AMD, why?
Tagging @gamersnexus.bsky.social
Half-Moon appears as if it's cut by cables dangling from a construction crane.
Another simple shot that I'm pretty happy with.
#photography #moon
I'm definitely interested in modding it to add Polish. My mom would love this game!
Defeated by web platform inconsistencies...
I made a small web component that glues an element to a physical pixel across fullscreen state changes. For reasons.
...But it only works on Windows, on the primary monitor, and Brave shields break it.
If you want to improve it - be my guest. I give up.
"'YOU WON'T BELIEVE'? Th–that doesn't mean anything, why would anyon—aaaand 80 thousand people shared it on Facebook."
From that image positioned directly below "Here's what to do instead", I initially thought you wanted to promote using carousels!
"Damian" works for me, thanks!
Polish (polski):
Poznaj sposoby tworzenia zachwycających interakcji z uroczymi detalami, z użyciem magii CSS, JavaScript, SVG i Canvas.
Zdradzam wszystkie moje triki!
None of the above are possible with links. The sender can modify what the link points to, fooling the initial scan by email client. Links will rot, like they always do. Linking requires me to do an action to keep the file. My email client won't scan the linked file's contents or preview them.
That post asks a question, but commenting is disabled - is that intended?
I vastly prefer attachments, because files are stored on the end I can control. No risk of link rot. The sender can't modify the file after sending (good for legal documents). Email client scans them and allows previews.
Does this work (even via cronjob) when you're in Deck's game mode?
There are games that like to crash and wipe your save (e.g. ZTD), so I'd love a hourly backup of specific titles, even during gameplay, without leaving game mode.
Yeah, every case is different. I like to mention that "delete repository" pattern when teaching about accessibility and preventing huge mistakes.
Thanks for the discussion!
Reserving space is tricky when you consider users who changed their root font size, need to support translations (e.g. German can be much longer than English), or have an error message that just can't be conveyed in a few words and needs more lines.
If it works well for the target audience, then sure! That's what's most important.
What I've learned from @adamsilverhq.bsky.social's Form Design Mastery course is that if you validate on submit, layout shifts aren't an issue. Users know how to scroll. And it would be best to break up a form into smaller parts if it has that many fields!
Even better - display hint text right below the label, above the input field, so that the text isn't covered by browser's autocomplete popup or a phone's virtual keyboard. Same for error messages.
Personally, if I really, really (really) have to use a segmented control, I insist on only using it if there are 3+ options to choose from, and I'm 100% sure people will know which option is selected.
I've seen way too many implementations with 2 options where it's not clear which one is selected.
Sad news, but instability is expected at this early stage of WCAG3.
APCA was quite a big improvement, and there are lots of a11y-related websites that assumed APCA is the future. Are there any plans to make a semi-official statement, so that this info gets around?
I expected the vanilla attr() to work with any property, but browsers limit it to the content of pseudoelements. :(
I started playing Talos Principle for the puzzles, and stayed for the plot. The sequel is even better and vastly expands the story with more characters and deeper philosophical questions, while you solve puzzles in beautiful environments. Such a lovely experience.
This reminded me of NaissanceE, where you have to repeatedly click to breathe, or you'll get winded...
youtu.be/yvmfKPtQn1E?...
I consider myself fairly knowledgeable about accessibility, yet I learned a TON more this year.
Latest thing: not removing borders from <button>s, because high contrast mode relies on them. You can make the borders transparent, just don't remove them completely. More details in the linked issue.