Chrome's built-in AI APIs provide the essential ingredients for web innovation → https://goo.gle/3TDXuB7 Like a barista's perfectly arranged setup, our APIs interacting with Gemini Nano empower you to create powerful applications. Whether you're translating content or generating insightful summaries, our task APIs streamline development to boost your project's potential.
Chrome for Developers
Technology, Information and Internet
Helping you build, grow, and innovate on the web.
About us
The official Chrome for Developers LinkedIn account from Google. We want to help you build beautiful, accessible, fast, and secure websites that work cross-browser, and for all of your users.
- Website
-
https://developer.chrome.com/
External link for Chrome for Developers
- Industry
- Technology, Information and Internet
- Company size
- 5,001-10,000 employees
Updates
-
CSS Nesting is improved with CSSNestedDeclarations. Now, declarations stay in place across Chrome 130, Firefox Nightly 132 and Safari Tech Preview 204. Learn more → https://lnkd.in/gyu8kkTa
-
Chrome for Developers reposted this
For those monitoring Core Web Vitals, we made a small change to the CrUX History API used by CrUX Vis last night and now return 10 months of data, rather than 6 months of data to bring it more inline with the CrUX Dashboard that we're looking to deprecate. Enjoy! https://lnkd.in/e83g9TT3 We didn't wanna break any CrUX tools out there, so kept the default at 25 weeks, but CrUX History API users can also request the full 40 weeks with the optional "collectionPeriodCount" request param: https://lnkd.in/erQq3SiS For those wanting longer history, we recommend using the CrUX BigQuery dataset for multi-year analysis (at an origin level): https://lnkd.in/edTk54SX But hopefully this small update will make the CrUX History API (and CrUX Vis) a little more useful for you all!
-
Chrome's secret weapon for smooth feature launches? It's Finch! This system helps Chrome engineers test and balance product updates safely. Learn about its use cases and explore this article to see its impact. → https://goo.gle/4hYNuM3
-
-
🔒 Browsing history is safer with Chrome 136 beta. Explore partitioning of :visited links & other cutting-edge updates—plus the introduction of several new enterprise features. Check it out→ https://goo.gle/4j5N5ZJ
-
-
🗓️ The March Baseline digest is here → https://goo.gle/4ckqJkI Don't miss out on these updates: ✅ ESLint's New Rule 🌐 Web Platform Dashboard Queries ✨ Newly Available Features
-
-
Learn about Chrome's new extension controls and how to prepare your extension→ https://goo.gle/43vaqz8 Explore the experimental new extensions menu and the addHostAccessRequest API, designed to empower users and boost trust.
-
-
The :visited selector is now more private in Chrome → https://goo.gle/3G6vzWu Chrome 136 introduces partitioning, making it the first major browser to obsolete attacks that reveal your browsing activity, enhancing security & privacy.
-
-
Chrome for Developers reposted this
We've published not one, not two, but THREE blog posts recently on all the goodness we've been working on to improve performance debugging in Chrome DevTools: 1. Improved navigation and filtering in the DevTools Performance panel https://lnkd.in/etP4Jgza 2. Insights sidebar in the DevTools Performance panel https://lnkd.in/ehG74weq 3. More accurate DevTools performance debugging using real-world data https://lnkd.in/ecBWzyG7 And, those are just the latest 3 in a series of posts on all the great work going on there (links at the top of each article in case you wanna catch up on the previous work). So many good things in here for your webperf nerds: - 🧭 Modern navigation - 🔍 Better zooming and filtering - 💡 Lighthouse Insights - right there in your trace!! - 💻 CPU calibration What's your favourite new feature and how has it helped you identify performance issues?
-