jamie.build
Comic books. Board games. Open source.
Prev: Babel, Yarn, Flow, Parcel, Biome
416 posts
1,904 followers
334 following
Regular Contributor
Active Commenter
comment in response to
post
It's cool that React-Aria provides things like onPress, but it shouldn't come at the cost of breaking pointer/keyboard events
- Pass all DOM events through to elements
- Stop calling stopPropagation() everywhere (continueProp()` doesn't solve the problems this creates)
- Forward refs to elements
comment in response to
post
(Context: Dude is picking a fight with the CEO of The Onion because he is?/was a journalist and he's dating some local political candidate)
bsky.app/profile/benc...
comment in response to
post
Here's a little demo of what I mean codepen.io/thejameskyle...
comment in response to
post
Billionaires could easily just go create more apps, throw millions around at every idea they have
But then if they fail they'd be confronted with the fact that their idea is something less than brilliant
(I would be so much better at being a billionaire, someone just give me a chance)
comment in response to
post
My take that has been controversial at the companies I’ve worked at, has been that this should just be a very large tooltip: non-interactive, descriptive of the content behind a link/button. So I would suggest a name like TooltipCard
comment in response to
post
Anything that borks up my app? You assume I can remember the implementation details of things I wrote 3 years ago
comment in response to
post
If you start on June 25, you can do every word of the song leading up to the final "it's gonna be me" on a separate day
comment in response to
post
You need to start this on May 2nd for next year
comment in response to
post
I haven’t done any cross browser testing outside of chrome since we’re an electron app, but for a tooltip component I had to fully wire it up together as if I was building it without popover. Which is fine I guess, the auto anchor behavior and top-layer is nice enough on its own
comment in response to
post
I take this back, it was easy enough to work around. But inspecting the accessibility tree and using a screenreader, it still requires a fair bit of wiring up with aria attrs
comment in response to
post
As CSS color syntax you mean?
comment in response to
post
Lucky for us we're an Electron app and only need to support the latest version of Chrome so we can immediately make use of anchor positioning
But I've been having trouble implementing this kind of containment using multiple anchors, and struggling to get it right. Can't find anyone doing this yet
comment in response to
post
Popover API might be dead on arrival actually. It’s just got a lot wrong with it already
comment in response to
post
Sometimes React-Aria doesn't even play well together with itself because they haven't explicitly added support for something. I had to drop some tooltips from the UI because it doesn't play well together with listboxes
comment in response to
post
I understand where you’re going with that, but actually the problems I want to solve that weren’t well solved by tuples and records (structured shared data, de/serialization, etc) are better solved by structs/enums and new data types
comment in response to
post
Deadmau5 really likes JavaScript
comment in response to
post
Yes, although I prefer valibot these days. Even with strict parsers like protobufs I need “as” a fair bit
comment in response to
post
I feel like “as” is a little too permissive. I often need something between “satisfies” and “as” even when working with strict parsing libraries like protobufs
comment in response to
post
Oh I hadn’t considered more than 3 parts, making it variadic is interesting
comment in response to
post
You can be any of these things, you just can’t be all three at once
comment in response to
post
I’ve mainly heard it being used by journalists for their work devices who may be targets of state cyberattacks, a thing that actually happens and has gotten people killed trying to protect the rights of people like you, to do things like post really mad
comment in response to
post
I think I saw it disables service workers too
comment in response to
post
Since people were so surprised by it disabling WASM, it also disables:
JIT Compilation, WebCodecs, IndexedDB, File/FileReader API, <embed>, Web Speech, WebLocks, and all experimental APIs
Maybe more too, they don’t seem to provide a full list anywhere
comment in response to
post
One solution is to put an element between .card-header/.card-image
.card-header { max-height: 200px; }
.card-header-inner { /* doesn't require any styles */ }
.card-image { max-height: 100%; /* ... */ }
But even with all that it's very fiddly, especially with non-img/video/svg/etc elements
comment in response to
post
I dislike that object-fit: contain is hiding that the aspect ratio of the .card-image has changed
You're then limited in what styles you can add to the image. Like if you tried to add a border-radius or box-shadow to the image it wouldn't
comment in response to
post
Youre just required to have a number like littledan.42
If you just keep deleting and retyping the last character you can keep trying for new numbers
comment in response to
post
Signal supports usernames now if you’d rather give that out than a phone number
comment in response to
post
Because people often combine multiple unions and it would generally not be great if it was hiding the fact that the type is *actually* string
comment in response to
post
Consider some systems weren’t designed with type systems in mind and do all sorts of weird string DSL stuff
comment in response to
post
I don’t know what to tell you other than this is sometimes the objectively correct type for describing other systems. But like go off
comment in response to
post
That’s not going to stop being true by just typing it “string”
Usually this trick is because you’re integrating with some other service/api not because you control both sides