Luke

Web Platform Engineer at Igalia

Cardiff, UK

Opinions my own

Website: https://lukewarlow.dev?utm_source=Mastodon
GitHub: https://github.com/lukewarlow
Pronouns: He/Him
Bluesky: https://bsky.app/profile/lukewarlow.dev

Public Key

npub1xwma2d0ss98ndngwuvljk43l5gulnsj7teqd564awcuq3dc7s63sl3gt5a

NIP-05 Address

lukew_at_toot.wales@momostr.pink

Profile Code

nprofile1qqsr8d74xhcgzneke58wx0et2cl6yw0ecf09usx6d27hvwqgku0gdgcprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqyxhwumn8ghj7mn0wvhxcmmvnnq33l

Publishing to

relay.snort.social

nos.lol

relay.damus.io

Author Public Key

npub1xwma2d0ss98ndngwuvljk43l5gulnsj7teqd564awcuq3dc7s63sl3gt5a

Show more details

Last Notes

2026-09-15 14:15:04 UTC

It looks like Google is finally working on a way to support third-party browsers being able to install proper APKs for web apps. This is generally something that only Chrome can do currently. There's very little public documentation and it still seems quite early, but there's a new WebAppManager API added in Android 17.
https://developer.android.com/reference/android/content/pm/webapp/WebAppManager

2026-03-25 08:00:59 UTC

- reply

ahh I see, yeah it doesn't help lots of people say it the wrong way too so it's hard to actually know.

2026-03-25 07:56:59 UTC

- reply

it's definitely said like veet, because it's french for quickly!

2026-03-09 13:54:06 UTC

- reply

yeah same behaviour here.

2026-03-09 13:15:01 UTC

- reply

okay scope_extensions might solve the use case for PWAs opting to keep some in-app. But it doesn't allow the user to choose external links to open in an actual browser rather than some chrome custom tabs UI.

2026-03-09 12:41:33 UTC

- reply

also while I'm here I'm gonna be awkward and ask that web APKs be opened up to other browsers. They're great but being chrome only is disappointing given how otherwise open Android is.

2026-03-09 12:37:19 UTC

- reply

so the issue here is external links out of that scope still open with an in-app browser. See below where I've clicked your link in my PWA of mastodon.
https://toot.wales/system/media_attachments/files/116/199/245/890/420/978/original/8651ed63879f1446.png

2026-03-09 12:24:21 UTC

- reply

alas I suspect this isn't specced at all. Specs only care about what is web observable and whether you're running "in-app" or in browser I don't think is available to you.
The concept of PWAs is itself probably not even really specified overall. I suspect this is just a Google decision with their web APK set-up for PWAs.

2026-03-09 12:03:30 UTC

- reply

it should be both user configurable but also pwa configurable. Like in mine I might want to keep my Auth domain "in scope" for navigation alongside my app scope but then also send everything else to the browser.

2026-01-12 13:16:03 UTC

An early look at the accessibility work going on in Servo. Part of Igalia's Sovereign Tech Fund project.
https://www.igalia.com/2025/10/09/Igalia,-Servo,-and-the-Sovereign-Tech-Fund.html
https://toot.wales/system/media_attachments/files/115/882/308/065/145/260/original/e84e6ae1170a887d.mp4

2025-09-04 14:49:16 UTC

- reply

$610 million is an insane amount of money for that? Or am I just out of touch?

2025-08-21 16:11:09 UTC

Just got command buttons enabled in stable on WebKit trunk!
Firefox recently sent out an intent-to-ship so hopefully by early next year they'll be available across the board.

2025-04-12 06:58:30 UTC

- reply

Ooh that's good to know! I didn't realise edge had added a contrast theme at the browser level. I knew about Firefox's but I suspect it's not used often. Though with some recent improvements it might be better.
Fwiw Android has relevant settings that you could add to your list if you wanted. Both High Text Contrast (supported for a while) and the newer Colour Contrast (soon, it's in nightly firefox and chrome) will work.

2025-04-11 20:55:11 UTC

- reply

Arguably the main source of the annoyance is actually Windows. Unlike every other OS (except Chrome OS), it doesn't have a standalone preference for high contrast. It's intrinsically tied to Contrast Themes (which are what provide colours for forced-colors mode).
forced-colors itself is also tricky to fully understand because it is in practice a Windows only feature.

2025-04-11 20:53:35 UTC

- reply

Nothing stops an OS from providing a low contrast preference, Android's setting is even setup at the API level to support this (-1 to 1 value range). It's just that no OS does this right now, so less isn't usable on its own.
The bit where the two features do have an overlap is the custom value which is conceptually tied to forced colors mode.
The fact forced-colors mode can change the prefers-contrast value isn't unique either, it also changes the prefers-color-scheme value too.

2025-04-11 20:46:52 UTC

@npub1ftx…yzsr
Making a new thread so it doesn't ping Adrian who wants a concrete resource for this. I would say that forced colours mode and prefers-contrast aren't actually as tightly coupled together as it might seem at first glance.
prefers-contrast works as a standalone media query with support on iOS, macOS, Android and some Linux distros. It just so happens to have two values that are only ever set as part of forced-colors mode.

2025-03-13 13:35:02 UTC

To follow up command invokers shipping in stable chrome 135, I just landed a flag flip to preview status in WebKit!
(Meaning they'll be on by default in Safari Tech Preview but not yet for Stable)

2025-03-07 10:58:18 UTC

- reply

it's a new thing we added recently. closedby=any will enable light dismiss. It's in chrome 134 and hopefully others this year.
You can prevent it by changing the value or you can listen to the dialog's cancel event and prevent default if you want to conditionally cancel it based on some state.

2025-02-19 17:33:27 UTC

Command Invokers are finally happening!
Chromium has an approved I2S and WebKit should be ready to ship to preview very soon.
Today it was merged into the HTML spec! https://html.spec.whatwg.org/multipage/form-elements.html#attr-button-command

2025-01-27 12:44:36 UTC

Are there any existing UI related features (CSS, JS or HTML) that aren't available cross-browser (either not implemented or buggy) that you wish were? If so can you say which and explain the use cases?
Specifically looking at existing things rather than new things you want (though feel free to share those too).
E.g. focus({focusVisible}) or hidden=until-found

2025-01-15 20:53:41 UTC

- reply

I hate that we have acceptable ranges and then doctors decide actually they're wrong and it's fine to be outside them...

2024-12-09 11:19:02 UTC

- reply

`color-scheme: light` when a user has explicitly chosen a scheme should probably actually be `color-scheme: light only` else chrome on Android may try and force it to dark mode anyway.

2024-11-21 17:24:02 UTC

Two new features for the HTML color input!
- an alpha attribute, allowing the user to select a translucent color.
- a colorspace attribute, allowing the author to choose between srgb and display-p3.
With either attribute present the value is a CSS color function instead of hex. Try it in STP 207!
https://cdn.masto.host/tootwales/media_attachments/files/113/522/098/223/272/899/original/121e3a213f0bf69c.png

2024-11-17 14:28:01 UTC

Two cool improvements are coming to <dialog> soon ™️.
- button command/commandfor attributes to open dialogs without JS.
- closedby attribute to enable light dismiss or disable close on esc (etc)

2024-08-02 11:12:59 UTC

- reply

I think you get the access token from GitHub (in security section iirc) and then use it instead of your password in that form. That's how logging into native apps sometimes works? Not 100% sure but worth a try.