lukewarlow.dev
💻 Web Platform Engineer at @igalia.com
🦆 Nature lover
🏴 Cardiff
628 posts
1,985 followers
691 following
Regular Contributor
Active Commenter
comment in response to
post
Congrats! They're lucky to have you!
comment in response to
post
Congratulations!
comment in response to
post
Slides of my talk @webengineshackfest.org - Bridging CommonJS and ESM in Node.js, or implementor's tales of require(esm)
github.com/joyeecheung/...
comment in response to
post
It's sunny enough! (We'll ignore the grey clouds I've cropped out)
comment in response to
post
Command/commandfor will almost definitely be shipped across the board before it opens, and appearance: base won't be specced fully in time (imo).
It is an interesting thing to think about.
comment in response to
post
By plane (unfortunately), the journey time via train is just a bit too long for me. Unfortunately there seems to be a gap in the high speed network between France and Spain which adds a bit of time and inconvenience to the system.
comment in response to
post
After experiencing London's 24°C today I'd happily take that tbh 😅
comment in response to
post
I read this a lot but it's something I've never really identified with. I can't say I've ever really cared why something has run? Like in Vue if I have a watcher for a value that does something as a result I can't say I've ever had to debug it doing something I didn't want? Am I missing something?
comment in response to
post
Depending on use case you don't even need an AST, or put another way the DOM and CSSOM is your AST.
comment in response to
post
You can potentially do a hop via MDN browser-compat-data which has the feature keys linked to various APIs, it's probably in a format you can use as a lookup from source code features.
comment in response to
post
We had a discussion in the joint task force today and *for now* we're dropping the element-backed status from the spec. This doesn't mean we won't one day make it one but there's a feeling that we should take things slow. Once CSS forms is more complete, i hope we can apply it to most/all of them.
comment in response to
post
@oliverdunk.com might be able to help?
comment in response to
post
I think inside of a container query and only when you're space limited is perhaps okay. As a default I think probably not.
comment in response to
post
Even with high contrast disabled the new UI is too light when in dark mode.
comment in response to
post
Btw your popovertarget fallback for command/commandfor only works if you put the popover attribute on the dialog element, but it's probably better to just fallback to JS because it's semantically different to be a modal dialog.
comment in response to
post
They're densely packed into a handful of places most of which are up north unfortunately! Only "southern" populations are Lundy, Isles of Scilly and a few islands off Pembrokeshire in Wales (Skomer being most famous).
comment in response to
post
We had some early discussions on giving us button commands to use instead of the ::scroll-button stuff when you need something more than the CSS stuff (or you just don't want to use the CSS stuff). Not sure what it will end up looking like yet.
github.com/openui/open-...
comment in response to
post
"you're incur in a security issue." 🤨
Unfortunately these kinds of rules stick around long past when they're needed. Security audits at my last job were so frustrating because they'd come back with so much nonsense. Stuff like disabling autofill on password inputs which doesn't work and is dumb.
comment in response to
post
I don't even wanna ask how that's a thing...
comment in response to
post
Step 1: npm uninstall next react <insert other garbage here>
Step 2: static position the top bar because why does it even stick...
comment in response to
post
Damn we're old...
comment in response to
post
Just as an fyi the demo video doesn't seem to actually play in chrome on Android. Works correctly in Firefox though so perhaps it's a slightly odd format?
comment in response to
post
Yeah we need an API to do it properly else it just makes for a worse experience.
comment in response to
post
Hard to detect that there even is a conflict, I'm not sure that the force dark mode is actually detectable via JavaScript.
comment in response to
post
Yup, browsers really miss the mark when it comes to user preferences.
The main thing I find is that sites with toggles set color-scheme to 'light' instead of 'light only' and the browser in this scenario will still force it to dark.
comment in response to
post
Good good, it sounds obvious I just wanted to make sure I wasn't missing something!
comment in response to
post
Thanks for letting me know! I'm in Spain for a work event that week though so won't be able to make it. I'll keep an eye out for future events though.
comment in response to
post
This is what I was thinking too I just notice essentially no-one does this. I think probably because they don't know/care how to rather than a deliberate decision though.