# Google Chrome Google Chrome is a fast, safe web browser for browsing the web across computers and mobile devices. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Security Week 2637: взлом Dropbox через Lenovo ID DevFeed: [Security Week 2637: взлом Dropbox через Lenovo ID]() Original publisher: [Read original article]() Author: Kaspersky\_Lab ("Лаборатория Касперского") Published: 2026-09-07T20:01:45Z Content type: news Language: ru Sources: ["Лаборатория Касперского" RU]() Topics: [Security](), [dropbox](), [Google Chrome](), [V8](), [OpenAI](), [WordPress](), [migration]() Tags: [chrome](), [dropbox](), [google-chrome](), [id](), [lenovo](), [news](), [openai](), [security](), [sql](), [tag-9fe8963de219](), [v8](), [wordpress]() ### AI overview A weekly security roundup reports that several thousand Dropbox accounts were compromised through flawed Lenovo ID authorization. It also covers ValleyRAT spyware, a Google Chrome V8 vulnerability, OpenAI agents making changes outside a test environment, Plex updates, and a WordPress plugin SQL injection. ### Source excerpt Как стало известно на прошлой неделе, несколько тысяч учетных записей в сервисе Dropbox были взломаны в период с 4 по 21 августа. Взлом стал возможен из-за некорректной авторизации при использовании стороннего идентификатора Lenovo ID. Как выяснилось позднее, ошибка на стороне Lenovo позволяла зарегистрировать учетную запись на произвольный почтовый адрес, а потом использовать ее для доступа к учетке с тем же электронным адресом в Dropbox. Dropbox отреагировала на инцидент, принудительно разлогинив всех пользователей, использовавших Lenovo ID в качестве метода авторизации. Также было добавлено обязательное требование ввода пароля непосредственно для учетной записи Dropbox. Читать далее ## Security Week 2623: слежка за пользователями через SSD DevFeed: [Security Week 2623: слежка за пользователями через SSD]() Original publisher: [Read original article]() Author: Kaspersky\_Lab ("Лаборатория Касперского") Published: 2026-06-01T17:31:16Z Content type: news Language: ru Sources: ["Лаборатория Касперского" RU]() Topics: [Security](), [Filesystems](), [Google Chrome](), [JavaScript](), [Linux](), [macOS]() Tags: [google-chrome](), [javascript](), [linux](), [mac](), [macos](), [security](), [side-channel](), [ssd](), [tag-9fe8963de219]() ### AI overview Researchers from Graz University of Technology described FROST, a browser-based contention side-channel attack that uses repeated SSD access through the Origin Private File System to infer running programs and visited websites from storage-performance delays. The attack runs in JavaScript without user intervention and was tested with Google Chrome on Linux and macOS systems. ### Source excerpt На прошлой неделе исследователи из Грацского технического университета в Австрии опубликовали научную работу, в которой предложили метод отслеживания пользовательской активности через браузер. Варианты атак, в которых вкладка с вредоносным сайтом может, например, определять, какие страницы открыты по соседству, предлагались и ранее, но полагались в основном на особенности работы браузеров. Новая атака FROST также использует особенности браузеров, но основным каналом утечки оказываются не они, а производительность накопителя данных. Общая схема атаки выглядит следующим образом: пользователя заманивают на вредоносную страницу, которая при помощи стандартных технологий браузеров реализует активный и регулярный обмен данными на SSD. Производительность SSD ниже, чем у оперативной памяти, что вызывает определенные задержки при обмене, когда к накопителю также обращаются другие программы и веб-сайты. Как выяснилось, паттерны этих задержек позволяют с достаточно высокой надежностью выявлять не только запущенные на ПК программы, но и посещаемые веб-сайты. Читать далее ## Squarespace & Web Standards: How We Helped Bring HTML Video & Audio Lazy Loading to Today's Browsers DevFeed: [Squarespace & Web Standards: How We Helped Bring HTML Video & Audio Lazy Loading to Today's Browsers]() Original publisher: [Read original article]() Author: Scott Jehl Published: 2026-03-30T21:00:00Z Content type: article Language: en Sources: [Squarespace](), [Squarespace Engineering Blog]() Topics: [web-standards](), [lazy loading](), [HTML](), [Web platform](), [WebKit](), [Chromium](), [Google Chrome](), [Firefox]() Tags: [browsers](), [chrome](), [chromium](), [firefox](), [html](), [lazy-loading](), [standards](), [web-standards]() ### AI overview Squarespace engineers describe how they helped add lazy loading for HTML video and audio to the HTML Standard. They contributed proposed implementations for Firefox and WebKit, worked with Chromium developers on a Google Chrome implementation, and added automated testing. ### Source excerpt At Squarespace, many of our core products are built on web standards, and our engineers are constantly pushing the boundaries of the web's capabilities. Occasionally, those boundaries reveal a limitation: an opportunity for the web's native capabilities to grow. This post is the story of how we found such an opportunity to work with the standards community to improve the web in a way that we - and everyone who uses it - can benefit. ## Speculative Optimizations for WebAssembly using Deopts and Inlining DevFeed: [Speculative Optimizations for WebAssembly using Deopts and Inlining]() Original publisher: [Read original article]() Author: Daniel Lehmann and Matthias Liedtke Published: 2025-06-24T00:00:00Z Content type: article Language: en Sources: [V8]() Topics: [WebAssembly](), [V8](), [JIT](), [Google Chrome](), [Compiler](), [JavaScript](), [Dart]() Tags: [benchmarks](), [code](), [compiler](), [dart](), [google-chrome](), [internals](), [javascript](), [jit](), [webassembly]() ### AI overview This V8 blog post describes speculative call_indirect inlining and deoptimization support for WebAssembly, shipped with Google Chrome M137. The optimizations use runtime feedback to generate better machine code, improving WebAssembly execution, especially for WasmGC programs. Dart microbenchmarks showed average speedups above 50%, while larger applications and benchmarks improved by 1% to 8%. ### Source excerpt In this blog post, we explain two optimizations for WebAssembly that we recently implemented in V8 and that shipped with Google Chrome M137, namely speculative call_indirect inlining and deoptimization support for WebAssembly. In combination, they allow us to generate better machine code by making assumptions based on runtime feedback. This speeds up WebAssembly execution, in particular for WasmGC programs. On a set of Dart microbenchmarks for example, the speedup by the combination of both optimizations is more than 50% on average, and on larger, realistic applications and benchmarks shown below the speedup is between 1% and 8%. Deoptimizations are also an important building block for further optimizations in the future. Background # Fast execution of JavaScript relies heavily on speculative optimizations. That is, JIT-compilers make assumptions when generating machine code based on feedback that was collected during earlier executions. For example, given the expression a + b, the compiler can generate machine code for an integer addition if past feedback indicates that a and b are integers (and not strings, floating point numbers, or other objects). Without making such assumptions, the compiler would have to emit generic code that handles the full behavior of the + operator in JavaScript, which is complex and thus much slower. If the program later behaves differently and thus violates assumptions made when generating the optimized code, V8 performs a deoptimization (or deopt, for short). That means throwing away the optimized code and continuing execution in unoptimized code (and collecting more feedback to possibly tier-up again later). In contrast to JavaScript, fast execution of WebAssembly hasn't required speculative optimizations and deopts. One reason is that WebAssembly programs can already be optimized quite well because more information is statically available as e.g., functions, instructions, and variables are all statically typed. Another reason is that ## The article criticizes Google's moderation of malicious Chrome Web Store extensions DevFeed: [The article criticizes Google's moderation of malicious Chrome Web Store extensions]() Original publisher: [Read original article]() Author: Wladimir Palant Published: 2025-01-13T13:12:43Z Content type: opinion Language: en Sources: [Almost Secure]() Topics: [Google Chrome](), [Browser Extension](), [Google](), [trust]() Tags: [extension](), [google-chrome](), [reports](), [transparency](), [trust]() ### AI overview This opinion article argues that Google's moderation of malicious and problematic Chrome Web Store extensions is ineffective and inconsistent. It describes automated moderation as inadequate, says legitimate add-on authors also face problems, and cites the author's experience reporting harmful extensions. ### Source excerpt Let's make one thing clear first: I'm not singling out Google's handling of problematic and malicious browser extensions because it is worse than Microsoft's for example. No, Microsoft is probably even worse but I never bothered finding out. That's because Microsoft Edge doesn't matter, its market share is too small. Google Chrome on the other hand is used by around 90% of the users world-wide, and one would expect Google to take their responsibility to protect its users very seriously, right? After all, browser extensions are one selling point of Google Chrome, so certainly Google would make sure they are safe? Unfortunately, my experience reporting numerous malicious or otherwise problematic browser extensions speaks otherwise. Google appears to take the "least effort required" approach towards moderating Chrome Web Store. Their attempts to automate all things moderation do little to deter malicious actors, all while creating considerable issues for authors of legitimate add-ons. Even when reports reach Google's human moderation team, the actions taken are inconsistent, and Google generally shies away from taking decisive actions against established businesses. As a result, for a decade my recommendation for Chrome users has been to stay away from Chrome Web Store if possible. Whenever extensions are absolutely necessary, it should be known who is developing them, why, and how the development is being funded. Just installing some extension from Chrome Web Store, including those recommended by Google or "featured," is very likely to result in your browsing data being sold or worse. Google employees will certainly disagree with me. Sadly, much of it is organizational blindness. I am certain that you meant it well and that you did many innovative things to make it work. But looking at it from the outside, it's the result that matters. And for the end users the result is a huge (and rather dangerous) mess. Contents Some recent examples The reporting process Chrome Web ## Fickle PDFs: exploiting browser rendering discrepancies DevFeed: [Fickle PDFs: exploiting browser rendering discrepancies]() Original publisher: [Read original article]() Author: Zakhar Fedotkin Published: 2024-07-09T12:51:22Z Content type: article Language: en Sources: [PortSwigger Research]() Topics: [pdf](), [browsers](), [Google Chrome](), [Firefox](), [Code]() Tags: [apache](), [article](), [browser](), [code](), [firefox](), [google-chrome](), [java](), [pdf](), [research]() ### AI overview The article explains how hybrid PDFs can exploit rendering discrepancies across browsers and PDF viewers. It demonstrates how widget annotations and interactive form fields can cause the same invoice to display different prices, and presents a proof of concept using the org.apache.pdfbox Java library. ### Source excerpt Imagine the CEO of a random company receives an email containing a PDF invoice file. In Safari and MacOS Preview, the total price displayed is GBP 399. After approval, the invoice is sent to the accounti ## A preview of CSS Container Queries DevFeed: [A preview of CSS Container Queries]() Original publisher: [Read original article]() Author: Kay Drechsler Published: 2022-02-07T00:00:00Z Content type: tutorial Language: en Sources: [Trivago]() Topics: [container](), [CSS](), [modern web development](), [Google Chrome](), [Chrome](), [web-standards]() Tags: [chrome](), [css](), [engineering](), [experimental](), [frontend](), [google-chrome](), [implementation](), [layout](), [performance](), [preview]() ### AI overview This article previews experimental CSS container queries, which let child elements respond to their parent element's available space and layout state. It explains how they can support responsive components without relying on JavaScript and notes their proposal-stage status and potential bugs. ### Source excerpt The still experimental feature of CSS container queries allows us to make child elements listen on the current layout state of their parent element via pure CSS declarations. With the recent implementation of Google Chrome's experimental flag for CSS container queries we're now able to play around with this upcoming feature and already get some insights into it. ## Google Chrome will soon let you follow your favorite websites DevFeed: [Google Chrome will soon let you follow your favorite websites]() Original publisher: [Read original article]() Author: Kishan Vyas Published: 2021-05-19T13:27:37Z Content type: news Language: en Sources: [XDA - RSS]() Topics: [Google Chrome](), [Chrome Canary](), [RSS Feed](), [Android](), [Google]() Tags: [android](), [blog](), [chrome-canary](), [follow](), [google](), [google-chrome](), [google-i-o-2021](), [new-feature](), [rss](), [xda-news-brief]() ### AI overview Google Chrome is testing a Follow button in Chrome Canary for Android that lets users subscribe to websites. Updates from followed sites will appear in a Following section on the New Tab page, using RSS feeds to retrieve new content. ### Source excerpt Google Chrome for Android is experimenting with a new feature that will let you subscribe to RSS feed of your favorite websites. ## Chrome extensions: Finding the missing proof DevFeed: [Chrome extensions: Finding the missing proof]() Original publisher: [Read original article]() Author: Mark R Bannister Published: 2020-04-17T00:00:00Z Content type: tutorial Language: en Sources: [Jane Street]() Topics: [Extension](), [Google Chrome](), [Linux](), [hosting](), [Tutorial](), [Development]() Tags: [browsers](), [building](), [chrome](), [extensions](), [hosting](), [install](), [linux](), [tutorial]() ### AI overview A tutorial on installing Chrome extensions hosted on an internal web server, with a focus on Linux and lessons that may apply to other operating systems. It explains external extension distribution and begins with building an example extension. ### Source excerpt Web browsers have supported custom plug-ins and extensions since the 1990s, giving users the ability to add their own features and tools for improving workflow or building closer integration with applications or databases running on back-end servers. ## Next.js 9.1.7 DevFeed: [Next.js 9.1.7]() Original publisher: [Read original article]() Author: Tim Neutkens Published: 2020-01-06T15:45:00Z Content type: release Language: en Sources: [Next.js Blog]() Topics: [Next.js](), [JavaScript](), [React](), [Google Chrome](), [Vercel](), [Testing]() Tags: [cli](), [google-chrome](), [javascript](), [next-js](), [performance](), [react](), [release](), [testing](), [upgrade](), [vercel]() ### AI overview Next.js 9.1.7 improves the framework with smaller client-side JavaScript bundles, clearer production build CLI output, built-in polyfills, faster page loading, support for stable ES2020 features, zero-configuration Vercel deployment, React Strict Mode compliance, and automated testing against nightly React builds. ### Source excerpt Next.js 9.1.7 improves upon a solid foundation, improving the enterprise-ready 9.1 release-channel. Upgrade for smaller client-side JavaScript bundles, redesigned CLI output, faster FCP/TTI, and more! ## Unlocalize Google Chrome Omnibar DevFeed: [Unlocalize Google Chrome Omnibar]() Original publisher: [Read original article]() Author: hi@meedamian.com (Damian Mee) Published: 2016-01-05T00:00:00Z Content type: tutorial Language: en Sources: [Damian Mee | Blog | Portfolio | About]() Topics: [Google Chrome](), [Google](), [Virtual Private Network]() Tags: [change](), [chrome](), [copy](), [domain](), [google](), [google-chrome](), [search](), [search-engine](), [settings](), [vpn]() ### AI overview A tutorial explains how to change Chrome's Google search-engine settings to prevent Google from redirecting users who travel frequently or use a VPN to a local domain they do not want. ### Source excerpt If you travel a lot or use a VPN, then at some point, Google might start to, wrongfully, think that you'd rather use some outdated local domain. Steps to fix it: Go to chrome://settings/searchEngines (copy-paste it into your address bar) In the Default search settings section find "Google" Rename Google to ex. Google (Annoying) in the 1st field Change google.com to ex. Google.annoying in the 2nd field Copy URL¹ from the 3rd field Scroll to the bottom of the Other search engines section Add a new search engine: Put Google into the 1st field Put google. ## W3C Push API Crash Course DevFeed: [W3C Push API Crash Course]() Original publisher: [Read original article]() Author: Nick Comer (nicholas@zumba.com) Published: 2015-05-29T00:00:00Z Content type: tutorial Language: en Sources: [Zumba]() Topics: [Chrome](), [notifications](), [W3C](), [Google Chrome](), [API](), [Google]() Tags: [api](), [chrome](), [google-chrome](), [notifications](), [push-notifications](), [w3c]() ### AI overview A tutorial introducing push notifications in Google Chrome through the W3C Push API. ### Source excerpt Getting started with push notifications in Google Chrome ## Fonts on Fedora Core 19 DevFeed: [Fonts on Fedora Core 19]() Original publisher: [Read original article]() Author: Michael Barker (noreply@blogger.com) Published: 2013-10-10T21:13:00Z Content type: tutorial Language: en Sources: [Bad Concurrency]() Topics: [Fedora](), [Font](), [Google Chrome](), [canonical](), [Unity]() Tags: [chrome](), [fonts](), [gnome](), [google-chrome](), [ubuntu](), [unity]() ### AI overview A step-by-step guide to improving font rendering on Fedora Core 19, including configuration for Google Chrome. ### Source excerpt I recently upgraded my personal workstation from Ubuntu 12.04 to Fedora Core 19. I'm very happy with the change, I prefer the standard Gnome 3 to Canonical's Unity desktop. Probably something to do with my workstation not being a tablet. However, one of the annoyances with Fedora Core has always been its font rendering. It was never as nice a default Ubuntu install. However after a couple of days of digging I've managed to figure out the magic incantation required to get all of my fonts looking good, including in Google Chrome. Read more " ## Multiple versions of Chrome on OS X DevFeed: [Multiple versions of Chrome on OS X]() Original publisher: [Read original article]() Author: gregers Published: 2011-04-07T13:37:45Z Content type: tutorial Language: en Sources: [Finn.no]() Topics: [Google Chrome](), [browser](), [Development]() Tags: [browser](), [chrome](), [developer](), [script](), [zip]() ### AI overview A tutorial for web developers on running stable, beta, and development versions of Google Chrome separately on OS X. It explains using custom profiles and wrapper applications, including installation and synchronization considerations. ### Source excerpt As a professional web developer you should use the bleeding version of Google Chrome, so you're prepared what your users will see a few weeks ahead. But the dev version tends to be a bit more buggy (naturally), and you have to test that your page works with both the beta and the stable version. Google Chrome has a command-line parameter to specify another profile, but it's a bit tricky to add command-line parameters to a Mac application. Yesterday I found a blog-post by Duo Consulting. They have made a nice little script that will generate an app with the profile you specify. I modified it a bit to allow running different versions of Google Chrome as well as a profile for each of them. To make the install process even easier for others I've zipped the generated applications (they just contain a script). Disclaimer: Each version will have it's own profile, so you have to set up each one from scratch with bookmarks, plugins and everything else. As Scott mentions in the comments, you can use the sync feature in Chrome to keep the installations in sync. First download each version and rename the original Google Chrome apps to "Google Chrome Stable", "Google Chrome Beta" and "Google Chrome Dev" and put them in Applications under your user folder. I.e.: /Users/gregers/Applications/ Unzip Chrome-Trio.zip(File removed) and put the apps in /Applications Don't select any of them as default browser, since that will use the default profile instead of the custom. Instead start Safari -> Preferences -> General -> Default web browser -> Select... -> Go to /Applications and choose the version of Chrome you want as default :) If you're interested in the script I used to make the wrapper-apps. You can find it here: http://pastebin.com/gPSdNi40 ## Google Chrome offers a smooth browsing experience despite rendering issues and limited plugins DevFeed: [Google Chrome offers a smooth browsing experience despite rendering issues and limited plugins]() Original publisher: [Read original article]() Author: Map Published: 2008-09-05T00:21:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Google Chrome](), [Google](), [Firefox](), [browser]() Tags: [browser](), [firefox](), [google](), [google-chrome](), [plugins]() ### AI overview The article gives a positive opinion of Google Chrome, describing it as smooth overall despite rendering problems and other oddities. It compares Chrome favorably with Internet Explorer and Safari, while noting that its lack of plugins is a current limitation and that Firefox can become sluggish with plugins enabled. ### Source excerpt Forget the benchmarks, forget whether its truly faster or slower, forget whether the market share is 30% for non-IE browsers (though is this only for US or internationally). Google Chrome evolution or revolution, whatever you want to call it, it makes me actually want to stay in the browser. I just want plugins, that function as well as the browser alone does. Yeah theres rendering problems, and some oddities, but the browser as a whole is smooth. I actually feel thus far its the best of IE and safari melded together. The only problem I see right now is the lack of plugins, which my guess is will come VERY SOON. Meanwhile firefox when having the plugins I want enabled can be sluggish, if Chrome plugins are of equivilant quality then I can't see how the browser wouldn't be at LEAST as smooth. Chrome really is a win for Google, whether they can monetize it or not. It helps them to keep people off the desktop and in the browser. I could go on for hours about bad moves they've made, such as picasa, but Chrome was actually a good one.