TypeScript excitement 😉
Congrats to @jakebailey.dev on updating upstream tsc to default to an unpinned *latest* yearly edition of ES20xx. Heading for TS 6.0 🎉
This mean less transpilation of new JS features & more use of native language features provided by JS engines 👍
github.com/microsoft/Ty...
You know that annoying experience on mobile websites where you need to find the little close button and can't swipe a menu closed?
The solution is simpler than you think.
With basic CSS scroll APIs, you can get built-in interruptible swipe gestures 🥳
The Chrome Identity and Payments team in Waterloo Canada is hiring several early/mid-career developers. I'm on the lookout for exceptional candidates with a passion for browsers and/or the identity/payments space! www.linkedin.com/posts/rick-b...
I started college in 2001, and from what I remember, that was about the time when you could easily find cliffs notes alternatives online for free, so that's why I didn't use cliffs notes in college.
Based on the story about your aunt, I'll restate my hypothesis to *at least 4 years* :)
I used cliffs notes in high school, which I guess means I’m about 4 years younger than you :)
Being an old-school web dev is always like "Oh wait, I *can* use container queries now"
There are many goodies that are newly and widely available in Baseline. backdrop-filter is so much fun to work with and I am obsessed with AVIF images and the ability to animate from display: none with @starting-style. And how easy is it to lazy load images now? web.dev/articles/bas...
View Transitions are now in all browsers! They also landed in React! developer.chrome.com/blog/view-tr...
Chrome for Android can now help users adopt passkeys more seamlessly.
If a user signs in with a saved password , your website can request that an associated password manager (in many cases on Chrome is Google Password Manager) creates a passkey automatically.
developer.chrome.com/blog/automat...
A lot has happened since Chrome shipped Same-Document View Transitions in 2023.
In 2024 we shipped Cross-Document VTs, added refinements such as `view-transition-class` and VT Types, and also welcomed Safari in adding VT support.
And this year … well, I wrote a post summing it all up.
If we started Chrome Dev Summit again, would you be interested in it?
(huh - apparently can't do polls here...), Please reply, Yes or No, or any other answer in between.
✅ Baseline now has full feature coverage, making it easier to know which web platform features are ready to use.
Build the next wave of Baseline-powered tools and compete for $10,000 in prizes → goo.gle/424SBWc
Announcing our public preview of Chrome DevTools MCP! Experience the full power of DevTools in your AI coding agent→ goo.gle/4pDE6Tk
With Chrome DevTools MCP, your AI agent can run performance traces, inspect the DOM, & perform real-time debugging of your web pages.
Before, you needed a plugin to use Baseline semantics in your Browserslist queries. Now you don't!
Just give it a target like `baseline widely available` and it'll work out of the box
Available in browserslist@4.26.0 and later
web.dev/blog/browser...
Show us your best tooling ideas to help developers adopt more modern web features!
Join the hackathon for your shot at $10,000 in cash prizes 🔥🔥
web.dev/blog/baselin...
Scoped View Transitions are ready for testing in Chrome!
SVTs expose el.startViewTransition() on HTML elements. The element creates a scope for the transition, ∴ the transition pseudo-elements are affected by ancestor clips and transforms. Multiple SVTs on separate elements can run *concurrently*.
🎉 Happy 30-month anniversary to Container Queries – in every browser since Feb, 2023. It was supposed to be impossible, but here we are!
Why 2.5 years? Nothing will change tomorrow, but Baseline uses this milestone to signal confidence a feature has gained "wide" support.
youtu.be/bhHV0rQ3-CQ
I know, I'm shocked as well!
Totally agree.
I'm not aware that it's a thing that has ever actually happened (though admittedly it would be hard to know if it did). But it's definitely something people are concerned could happen.
Here's one example (and I've heard others express similar concerns): bsky.app/profile/zach...
But IMO anyone who understands how to use progressive enhancement is likely not going to be confused or dissuaded by Baseline labels.
The primary audience for Baseline labels are people that *don't* fully understand progressive enhancement and aren't actively looking to try out new features.
The specific concern I've heard is that adding Baseline labels to blog posts and reference documentation will scare people off from using "limited availability" features, even if those features can easily be used as progressive enhancements now...
If you want to find out what Baseline target makes the most sense for your site, there are a number of tools to help you determine that: bsky.app/profile/deve...
And if you work at a company that doesn't have a browser support policy, talk to them about Baseline! #WhatsMyBaseline
Using Baseline 2023 as my browser support target means I can safely adopt TONS of great features, including:
- :has()
- Container Queries
- CSS Nesting
- linear() easing
Any many more: webstatus.dev?q=baseline_d...
Baseline Report Table, generated via: https://chrome.dev/google-analytics-baseline-checker/ Baseline target, % of users supporting 2015, 100.0% 2016, 100.0% 2017, 99.9% 2018, 99.8% 2019, 99.8% 2020, 99.8% 2021, 99.3% 2022, 99.2% 2023, 98.2% 2024, 96.0% Widely Available, 98.9% Newly Available, 87.5%
I believe this will lead to FASTER feature adoption on the web, not slower.
I also bet there are many features you can safely use now that you may not realize. For example, on my personal website, 98.2% of my users are on browsers that support all of Baseline 2023.
Here's what my data looks like:
BUT, if your company has a browser support policy, the decision is simple.
This is why I'm excited about Baseline.
Baseline makes it easier for companies to decide on a browser support policy. And with Baseline data now exposed in so many tools and resources, devs can easily follow that policy.
In this situation, most devs will give up. Or worse, many won't even try at all because they don't want the hassle.
I've seen this play out many times, even with features that have been available for 5+ YEARS!
Unfortunately, if a feature is not already in the codebase, it will face resistance.
Even if you convince your immediate teammates, is that enough? Do you need sign-off from a manager? Your CTO? Who is the final decision maker?
And what if your code breaks a customer, will it get reverted and then you'll just end up having to rewrite it anyway?
Here's the scenario:
You get assigned a ticket, research a solution, and find a new Web API that does exactly what you need. But in the PR your teammates ask:
- Are you sure we can use this?
- Did you check browser support?
- Is this used anywhere else?
Now you’re on the hook to justify it.
In my experience, one of the main reasons devs don't use new web features is NOT lack of browser support, it's because their company doesn't have a clear browser support policy.
Without a clear policy, the path of least resistance is to just NOT adopt any new features, even widely available ones.
I know some people in the web community are concerned that Baseline will discourage devs from using new features—or anything not "Widely Available".
Personally, I'm not worried about that at all. If anything, I think Baseline will speed up new feature adoption!
Here's why 🧵
