Eric Bidelman

Blazing fast.

Yes! Official versions of Chrome for automated testing that you can easily pin to a version. Your CI env will be happy.

A `scrollend` event is finally coming to the web! Sometimes the smallest additions are the most exciting and...useful. developer.chrome.com/blog/scrollend…

Lazy web, what's the best drop-in "Please upgrade your browser" widget these days?

RIP html5rocks! Definitely a highlight in my career. Proud of the entire team over the yrs. A global group of web devs producing some of the very best content EVER! It was such a joy to be part of it all since day 1, inspire so many, and see a community catalyze in the process.

@maxkoretskyi_ @rachelandrew MDN says it's supported. But that article is 12+ years old. Likely things have changed since Chrome 3 :)

@chrisota Def Getty/Getty Villa (two diff things), Huntington library (botanical gardens), Grand Central market DTLA, Original farmers market. So many good reccos.

✈️ Debating on working from LA for a week or so in May. What’s good? It’s been years since I’ve been there and have done most of the bucket list items (Disney, LACMA, Griffith, Eames House, Little Tokyo, the pier). Would love to meet some tweeps IRL also 🙌 ☕️🍺

LazyWeb: any way for a web app to feature detect that the "Allow Notifications" OS setting has been turned off? If the user previously gave access (Notification.permission === 'granted'), it would be useful signal to help educate users on how/where to re-enable.

@TimvdLippe @ChromiumDev @beverloo @ChromiumDev any guidance on this?

@ebidel @ChromiumDev CC @beverloo

Did web notifications get WAY less useful + engaging on Android 12? Seems the default now is to not show as a pop-up banner. Instead just a little icon in the status bar that's easy to miss :( Users are not going to find these settings. cc @ChromiumDev

@RichFelker @tomayac @steren @ChromiumDev Features we'd expect the majority of users to want (location for precise pickup, no typing) still end up having low acceptance rates. There's also the ever changing landscape of how each browser shows the permission UI + diffs btw desktop/mobile. Users constantly need to relearn.

@ebidel @tomayac @steren @ChromiumDev "Conversion rates" is an explicitly user-hostile metric. If you don't expect the vast majority of users to actively want the permission gated function without being "converted" you shouldn't be asking for it in the first place.

💡 Most permission prompts are ignored or dismissed. Taking this into account, Chrome's introduced a new blue permissions chip 🔵 that makes unwanted prompts less annoying to deal with, while not breaking wanted prompts. @tomayac's post has all details: developer.chrome.com/blog/permissio….

@thinmatt JiraTok. Do it!

Hello. I am a product designer... And I don't mind using JIRA.

@elado Found #introduction" target="_blank" rel="nofollow noopener">web.dev/granular-chunk… which describes the problem. Next's default setup for SplitChunksPlugin is #L352-L429" target="_blank" rel="nofollow noopener">github.com/vercel/next.js…, which splits libraries > 160KB into their own chunk. So everything is ending up there. Now to figure out how best to override!

@elado Yea was thinking it's one of these routes! Been too lazy to throw in a lot of exploration before asking the WebAtLarge :)

Webpack/NextJS experts. I have a tree shakeable npm lib used across our app. Some large components only get used on a few pages. Next still bundles them with the lib bundle. Since most pages don't them, they hurt perf. What's the magic to keep them out, only load on needed pages?

@DanielKempner I think we're good on tree shaking. What's not working well is how Next creates bundles for shared libraries used across pages. Example of what I'm talking about: gist.github.com/ebidel/2964a01…

@ebidel also remember that if there's any ambiguity on if the lib has side effects, webpack will automatically bundle everything. circular dependencies also throw it off

@bsmldrs If they get used _anywhere_ they end up in the same bundle. Thinking we need to mess with next's defaults for #splitchunksplugin" target="_blank" rel="nofollow noopener">webpack.js.org/guides/code-sp…. Also don't want other teams needing to remember to write dynamic imports when consuming our core library :(

@bsmldrs Yep, we're dynamically loading the components on pages which consume the large bits from libA. My expectation was that Next/webpack wouldn't bundle those things with rest of libA.bundle.js, but instead, create a sep chunk. But that's not the case.

@darin_hensley Dan. @jeffposnick @Paul_Kinlan might be able to help.

@ebidel Hello, devwebfeed.appspot.com went offline. Do you know who I could contact to request it be brought back at Google? It was very useful.