Thomas Steiner (@tomayac)

Now at @tomayac@toot.cafe

The below is an off-site archive of all tweets posted by @tomayac ever

February 17th, 2022

@gregwhitworth This sounds like it could be of interest to @denladeside.

via Twitter Web App

@kennethrohde @CharlieCroom @rauschma Maybe the current behavior could just be changed, so links always open in the default browser (the same way `_blank` now automatically implies `rel=noopener`) and pages that need to stay in the app need to explicitly

via Twitter Web App

@mtomweb @rauschma In your example this would require the PWA to capture links from oauth.com, which may not work if oauth.com is used by more than just your PWA, which most commonly will be the case.

via Twitter Web App in reply to mtomweb

@dgrammatiko Try installing https://t.co/AI5Xrg8rWD on desktop or mobile and see what happens for the different links. It’s for all those use cases (and more: that is, the default browser part).

via Twitter Web App

@dgrammatiko Can you say why you feel this way?

via Twitter Web App

@RReverser @mchcopl Yes, you can argue either way. The way it works today definitely isn’t right. I came from the fact that _authors_ can determine the value of `target` today, but (power) _users_ can always override (e.g., via middle-click to always open

via Twitter Web App

@kennethrohde @rauschma My proposal is that these links would open in Firefox for you if Twitter were to annotate all links (that is, links in tweets) with `target=”_default-browser”` in your example.

via Twitter Web App

WasmWeekly LibreOffice running within the browser using WebAssembly

lab.allotropia.de/wasm/ pic.twitter.com/zWEPPbwpin

via TweetDeck (retweeted on 11:07 AM, Feb 17th, 2022 via Twitter Web App)

@beth_panx @nitya @harshitgarg22 @ThePracticalDev Thanks a lot for adding this. It’s a valid feed with some warnings. Validated by pasting the RSS file into https://t.co/G2HmeBYwTo. https://t.co/ypuA5yHmol

via Twitter Web App

@rauschma Yeah, getting this right for everyone will be hard. Maybe a reason for more power user settings.

via Echofon in reply to rauschma

@JohnMu Also see the second part for when current=default:
“A side effect of this would also be that if browser A happens to be the default browser that links would then not open in the in-app browser experience of the installed PWA, but just in a regul

via Echofon

RT @philwalton: 🔢 If you’re passionate about Web Performance, and you want to help developers around the world improve, my team on Chrome i…

via Echofon

RT @simonhearne: Survivorship bias in #WebPerf - why your data may be lying to you and why FCP is a key metric to optimise for.
Slow users…

via Echofon

@rauschma Some flows like OAuth might make it desirable to stay in the in-app browser. But I tend to agree that in general the default browser should be respected.

via Twitter for iPhone in reply to rauschma

@brucel Maybe @Snugug has an idea or can route to someone who knows the answer?!

via Echofon in reply to brucel

@zachleat @SaraSoueidan As we’re renaming things, can I vouch for `document.qwertySelector()`?

via Echofon in reply to zachleat

@mchcopl The proposed `target` attribute value would make the desire explicit. I think it’s fair leaving this to authors, just like today where they can choose if they want links to open in a new tab (`_blank`) , or replace the current page (no value).

via Twitter for iPhone in reply to emceeMCtwo

RT @maudnals: Third-party cookies 🍪 will be phased out in Chrome. But things like third-party chat embeds rely on cookies to save interacti…

via Echofon

⁉️ Imagine a user installs a PWA using Browser A. Further imagine the user’s default browser is Browser B.

Should there be a new browsing context name or keyword “_default-browser” that forces links from a PWA installed via Browser A to open in Brows

via Twitter Web App