Alexandre Dieulot

@blue2blond @ID_AA_Carmack @t3dotgg Here’s my implementation: #L263" target="_blank" rel="nofollow noopener">github.com/instantpage/in… (disabled by default as it messes with other JavaScript events, and it’s not widely tested)

@blue2blond @ID_AA_Carmack @t3dotgg I’m referring to just triggering click on mousedown, to be clear. You can make mousedown progressive enhancement: mousedown, if it happens, triggers click. Click works normally, except it’s prevented if it was already triggered by the mousedown hackery.

Both @ID_AA_Carmack and @t3dotgg haven't heard about web #accessibility nor #INP nor #UX / user expectation. Mousedown is only faster if you allowed yourself or your framework to mess up the browser's main thread. Don't follow their advice. Optimize #JS #performance instead.

@tunetheweb Even same-origin is naively believed to be a problem. uBlock Origin has intended to block prefetching for ages (mainly for cross-origin I believe) but the setting was broken in Chromium until ~2 years ago. 😅

@Dieulot Ah. Well uBlock Origin extension also blocks Speculation Rules (which causes it's own confusion btw!). This API is mostly intended for (and of most benefit for) same-origin navigations but even with cross-origin it's more privacy preserving than <link rel=prefetch/prerender>.

My Google I/O talk "From fast loading to instant loading" about the Speculation Rules API is now live! youtube.com/watch?v=bSua9v… Hit me up if you have ay questions #webperf

@tunetheweb @iSaumya Should be next month in a new major version. 🤞🏼

@iSaumya @Dieulot Already merged! Should be in next version. github.com/instantpage/in…

30 mins to kick off for those at #googleio! Video will be released tomorrow morning (Pacific Time) for those not and be available here: io.google/2024/explore/2…

Act on press This is a UI design hill I will die on, and it dismays me how often and hard I have had to fight for it. Almost all interaction methods have a “press” and “release” event associated with them. Whenever possible, you should “do the thing” when you get the press event instead of waiting for the release event, because it makes the interaction feel substantially more responsive, and it reduces user errors by not allowing the focus to slide out of the hot box between press and release. Even a “ballistic tap”, where your finger is intentionally bouncing off the button or touch surface, involves several tens of milliseconds delay between the press and release, and most button presses have well over a hundred ms dwell time. There is a delight in interfaces that feel like they respond instantly to your wishes, and the benefit to every single user is often more important than additional niche features. Game developers, with simple UI toolkits, tend to get this right more often, but “sophisticated” app designers will often fight hard against it because it is mostly incompatible with options like interactive touch scrolling views, long press menus, and drag and drop. Being able to drag scroll a web page or view with interactive controls in it is here to stay, and nets out way better than having to use a separate scroll bar, but there are still tons of fixed position controls that should act on press, and it is good UI design to favor them when possible. In the early days of mobile VR, the system keyboard was a dedicated little OpenGL app that responded instantly. With full internationalization it became prudent to turn it into a conventional Android app, but the default act-on-release button behavior made it feel noticeably crappier. The design team resisted a push to change it, and insisted on commissioning a user study, which is a corporate politics ploy to bury something. I was irritated at how they tried to use leading questions and tasks, but It still came back one of the clearest slam-dunks I have seen for user testing – objectively less typos, expressed preference, and interview comments about the act-on-press version feeling “crisper” and “more responsive”. So, I won that one, but the remaining times I brought it up for other interfaces, I did not, and you still see act-on-release throughout the Meta VR system interfaces.

@yoavweiss Yep, the idea of using a one-liner cross-origin import() in a safe and non-blocking way is appealing.

Trying to gather a web developer signal - do y'all care about subresource integrity for dynamic imports?

@TimVereecke @stoyanstefanov Thanks. Do you know how much perf you’d be losing without caching with instantpage/specrules? My general recommendation for dynamic pages is to disable or drastically reduce caching, hoping that just-in-time preloading has the same benefit as caching in 90%+ of cases.

@stoyanstefanov FYI @yoav as we discussed this challenge several times 🙂 @Dieulot as I reference instant.page

🪩 Web Performance calendar day 18 🔗 calendar.perfplanet.com/2023/rli/ 🎨 Saving people from frustration *while* improving LCP is what Tim Vereecke (@TimVereecke) likes to do 🧐 Here is his intro to Recently Logged-In Users Browser Cache Bypassing with a dash of Speculation API #webperf

@shadeed9 @dimboump It’s enabled in Firefox 121, shipping in 11 days! bugzilla.mozilla.org/show_bug.cgi?i… developer.mozilla.org/en-US/docs/Moz… whattrainisitnow.com

@dimboump As per caniuse it's supported, but not sure if it's behind a flag or not: caniuse.com/css-has

I'm refactoring some CSS and I feel happy each time I use CSS :has() to replace old CSS. :has() is one of the best CSS features 👌🏼

@firt I love how it often doesn’t register the last key I type in the address bar on a 2020 Intel Mac. (I use it sparingly.)

Is it just me or Safari 17 on macOS is becoming unusable as main browser? After a few hours of usage: 1) I have several ghost tabs, they have a title and favicon but no loaded page inside 2) videos don't get played anymore 3) background tabs are reloaded on every return

@jasonfried Do you have a fleshed out rationale for putting icon labels on the right? It weakens usability as it makes your eyes zigzag.

One of the things we're aiming to do with ONCE.com products is make them as worldwide-ready as possible, right out of the box. This means using universal icons and self-explanatory concepts/UI everywhere we can, but, when words are absolutely necessary, we cycle through translations in-place. This way we don't need distinctly localized versions or extensive language packs. Rather, a single version is universally localized in the most common languages, with no configuration required. For example, here's the password field in our first upcoming ONCE product.

@vatsal_manot @krzyzanowskim When I tried to figure out why entry-level AppKit books were so sparse/outdated, I stumbled upon one of the big macOS publishers explaining that “unfortunately the market is complicated”. For entry-level books with no competition. 🤯

@krzyzanowskim Sadly probably true.

Are people still writing high-quality blogs/books on macOS app development in 2023?

@localhost_droid @mobtec May we know why it’s been deleted?

Prefetching techniques can improve page load time and positively impact business metrics. Learn how prefetching helped Terra increase ads click-through rate by 30% and speed up Largest Contentful Paint. by @mobtec and ⁦@localhost_droid⁩ web.dev/terra-prefetch…

@anatudor I can’t imagine an icon succesfully communicating “default theme”, so just text. (In which case those options would need to be separated by a vertical bar or something.)

So... you'd use ☀️ for light theme, 🌙 for dark theme... what icon would you use for auto/ default? Very serious question, btw. I can code it, I'm stuck on what icon to pick...

@anatudor @LukyVJ There’s a 12 years old bug in Safari at play here. bugs.webkit.org/show_bug.cgi?i… Appending “ 100.1%” to --lst or similar bullshit fixes it.

@LukyVJ You start by opening the image in a new tab, bringing up Firefox DevTools... twitter.com/anatudor/statu… Quick & dirty midnight version codepen.io/thebabydino/pe…

🥹

Here are the slides I presented this week on speculative loading (prefetch and prerender): #slide=id.gc6f9e470d_0_0" target="_blank" rel="nofollow noopener">docs.google.com/presentation/d… They include performance data on how beneficial these features are, from some partners and from Chrome's own in-the-wild metrics!

@HenriHelvetica Did that 7+ and its aging battery throttle for you? My 6s+ throttled hard, even for simple stuff like typing. Ludicrously bad.

After what feels like an eternity + 1 day, I'm going to finally replace my iPhone 7 Plus. Deciding between (in likely order): 15 Plus, 14 Plus or 13 Pro Max. I don't mind the idea of usb-c on the 15, giving it an edge on the 14 + can also get a 13 Pro Max refurb'd from Apple 🤔

@tunetheweb No surprise indeed. 🥲

@Dieulot :-( Perhaps not surprising as does seem a little late to be honest given it'll be released soon.

“Enabled Fetch Priority by default” Woo hoo! Just in time for Safari 17?