# Google Chrome

Published articles for Google Chrome.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Google Is Testing a Search Bar That Works Outside Chrome

DevFeed: [Google Is Testing a Search Bar That Works Outside Chrome](<https://devfeed.tech/articles/google-is-testing-a-search-bar-that-works-outside-chrome-9270.md>)

Original publisher: [Read original article](<https://webdesignerdepot.com/google-is-quietly-testing-a-search-bar-that-works-outside-chrome/>)

Author: Simon Sterne

Published: 2026-09-10T16:00:00Z

Content type: article

Language: en

Sources: [Web Designer Depot](<https://devfeed.tech/sources/web-designer-depot.md>)

Topics: [Chrome](<https://devfeed.tech/topics/chrome.md>), [Google](<https://devfeed.tech/topics/google.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-assistants](<https://devfeed.tech/tags/ai-assistants.md>), [ai-search](<https://devfeed.tech/tags/ai-search.md>), [ai-tech](<https://devfeed.tech/tags/ai-tech.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browser-design](<https://devfeed.tech/tags/browser-design.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [chrome-canary](<https://devfeed.tech/tags/chrome-canary.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [everywhere-omnibox](<https://devfeed.tech/tags/everywhere-omnibox.md>), [future-of-browsers](<https://devfeed.tech/tags/future-of-browsers.md>), [future-of-search](<https://devfeed.tech/tags/future-of-search.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [gemini-in-chrome](<https://devfeed.tech/tags/gemini-in-chrome.md>), [google](<https://devfeed.tech/tags/google.md>), [google-chrome](<https://devfeed.tech/tags/google-chrome.md>), [google-search](<https://devfeed.tech/tags/google-search.md>), [project-loom](<https://devfeed.tech/tags/project-loom.md>), [search](<https://devfeed.tech/tags/search.md>), [search-technology](<https://devfeed.tech/tags/search-technology.md>), [ui-design](<https://devfeed.tech/tags/ui-design.md>), [ux-design](<https://devfeed.tech/tags/ux-design.md>), [web-browsers](<https://devfeed.tech/tags/web-browsers.md>), [web-design](<https://devfeed.tech/tags/web-design.md>)

### AI overview

Google is testing Project Loom, an experimental floating Search bar that can appear over other Windows apps instead of remaining inside Chrome. The feature is unfinished, with screen sharing, Lens, and AI Mode controls reportedly not yet working.

### Source excerpt

Google is quietly testing a way to bring Search outside Chrome and directly on top of whatever app you're using. It's called Project Loom, and this little floating search box could hint at a much bigger future where Google follows you around your desktop.

## Security Week 2637: взлом Dropbox через Lenovo ID

DevFeed: [Security Week 2637: взлом Dropbox через Lenovo ID](<https://devfeed.tech/articles/security-week-2637-dropbox-lenovo-id-23094.md>)

Original publisher: [Read original article](<https://habr.com/ru/companies/kaspersky/articles/1079346/>)

Author: Kaspersky\_Lab ("Лаборатория Касперского")

Published: 2026-09-07T20:01:45Z

Content type: news

Language: ru

Sources: ["Лаборатория Касперского" RU](<https://devfeed.tech/sources/ru-2.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [dropbox](<https://devfeed.tech/topics/dropbox.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [V8](<https://devfeed.tech/topics/v8.md>), [OpenAI](<https://devfeed.tech/topics/openai.md>), [WordPress](<https://devfeed.tech/topics/wordpress.md>), [migration](<https://devfeed.tech/topics/migration.md>)

Tags: [chrome](<https://devfeed.tech/tags/chrome.md>), [dropbox](<https://devfeed.tech/tags/dropbox.md>), [google-chrome](<https://devfeed.tech/tags/google-chrome.md>), [id](<https://devfeed.tech/tags/id.md>), [lenovo](<https://devfeed.tech/tags/lenovo.md>), [news](<https://devfeed.tech/tags/news.md>), [openai](<https://devfeed.tech/tags/openai.md>), [security](<https://devfeed.tech/tags/security.md>), [sql](<https://devfeed.tech/tags/sql.md>), [tag-9fe8963de219](<https://devfeed.tech/tags/tag-9fe8963de219.md>), [v8](<https://devfeed.tech/tags/v8.md>), [wordpress](<https://devfeed.tech/tags/wordpress.md>)

### 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](<https://devfeed.tech/articles/security-week-2623-ssd-23075.md>)

Original publisher: [Read original article](<https://habr.com/ru/companies/kaspersky/articles/1042288/>)

Author: Kaspersky\_Lab ("Лаборатория Касперского")

Published: 2026-06-01T17:31:16Z

Content type: news

Language: ru

Sources: ["Лаборатория Касперского" RU](<https://devfeed.tech/sources/ru-2.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Filesystems](<https://devfeed.tech/topics/filesystems.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [macOS](<https://devfeed.tech/topics/macos.md>)

Tags: [google-chrome](<https://devfeed.tech/tags/google-chrome.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [macos](<https://devfeed.tech/tags/macos.md>), [security](<https://devfeed.tech/tags/security.md>), [side-channel](<https://devfeed.tech/tags/side-channel.md>), [ssd](<https://devfeed.tech/tags/ssd.md>), [tag-9fe8963de219](<https://devfeed.tech/tags/tag-9fe8963de219.md>)

### 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 ниже, чем у оперативной памяти, что вызывает определенные задержки при обмене, когда к накопителю также обращаются другие программы и веб-сайты. Как выяснилось, паттерны этих задержек позволяют с достаточно высокой надежностью выявлять не только запущенные на ПК программы, но и посещаемые веб-сайты. Читать далее

## Speculative Optimizations for WebAssembly using Deopts and Inlining

DevFeed: [Speculative Optimizations for WebAssembly using Deopts and Inlining](<https://devfeed.tech/articles/speculative-optimizations-for-webassembly-using-deopts-and-inlining-3533.md>)

Original publisher: [Read original article](<https://v8.dev/blog/wasm-speculative-optimizations>)

Author: Daniel Lehmann and Matthias Liedtke

Published: 2025-06-24T00:00:00Z

Content type: article

Language: en

Sources: [V8](<https://devfeed.tech/sources/v8.md>)

Topics: [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [V8](<https://devfeed.tech/topics/v8.md>), [JIT](<https://devfeed.tech/topics/jit.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Dart](<https://devfeed.tech/topics/dart.md>)

Tags: [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [code](<https://devfeed.tech/tags/code.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [dart](<https://devfeed.tech/tags/dart.md>), [google-chrome](<https://devfeed.tech/tags/google-chrome.md>), [internals](<https://devfeed.tech/tags/internals.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [jit](<https://devfeed.tech/tags/jit.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### 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](<https://devfeed.tech/articles/chrome-web-store-is-a-mess-36623.md>)

Original publisher: [Read original article](<https://palant.info/2025/01/13/chrome-web-store-is-a-mess/>)

Author: Wladimir Palant

Published: 2025-01-13T13:12:43Z

Content type: opinion

Language: en

Sources: [Almost Secure](<https://devfeed.tech/sources/almost-secure.md>)

Topics: [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [Browser Extension](<https://devfeed.tech/topics/browser-extension.md>), [Google](<https://devfeed.tech/topics/google.md>), [trust](<https://devfeed.tech/topics/trust.md>)

Tags: [extension](<https://devfeed.tech/tags/extension.md>), [google-chrome](<https://devfeed.tech/tags/google-chrome.md>), [reports](<https://devfeed.tech/tags/reports.md>), [transparency](<https://devfeed.tech/tags/transparency.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### 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

## Testing a React App in Chrome with Heroku CI

DevFeed: [Testing a React App in Chrome with Heroku CI](<https://devfeed.tech/articles/testing-a-react-app-in-chrome-with-heroku-ci-26500.md>)

Original publisher: [Read original article](<https://www.heroku.com/blog/testing-react-app-chrome-heroku-ci/>)

Author: Julián Duque

Published: 2024-09-24T20:11:00Z

Content type: tutorial

Language: en

Sources: [Heroku](<https://devfeed.tech/sources/heroku.md>)

Topics: [React](<https://devfeed.tech/topics/react.md>), [Heroku](<https://devfeed.tech/topics/heroku.md>), [ci](<https://devfeed.tech/topics/ci.md>), [Playwright](<https://devfeed.tech/topics/playwright.md>), [Puppeteer](<https://devfeed.tech/topics/puppeteer.md>), [Headless Browser](<https://devfeed.tech/topics/headless-browser.md>), [Testing](<https://devfeed.tech/topics/testing.md>), [Jest](<https://devfeed.tech/topics/jest.md>), [web applications](<https://devfeed.tech/topics/web-applications.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [ci](<https://devfeed.tech/tags/ci.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [download](<https://devfeed.tech/tags/download.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [github](<https://devfeed.tech/tags/github.md>), [google-chrome](<https://devfeed.tech/tags/google-chrome.md>), [guide](<https://devfeed.tech/tags/guide.md>), [heroku](<https://devfeed.tech/tags/heroku.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [jest](<https://devfeed.tech/tags/jest.md>), [react](<https://devfeed.tech/tags/react.md>), [testing](<https://devfeed.tech/tags/testing.md>), [unit-testing](<https://devfeed.tech/tags/unit-testing.md>), [web-applications](<https://devfeed.tech/tags/web-applications.md>)

### AI overview

This tutorial explains how to run end-to-end tests for a React application in Heroku CI using headless Chrome, Jest, and Puppeteer. It covers automating tests for a simple form-based application and configuring the application and test scripts for CI execution.

### Source excerpt

When building web applications, unit testing your individual components is certainly important. However, end-to-end testing provides assurance that the final user experience of your components chained together matches the expected behavior. Testing web application behavior locally in your browser can be helpful, but this approach isn't efficient or reliable, especially as your application grows more [...] The post Testing a React App in Chrome with Heroku CI appeared first on Heroku.

## Fickle PDFs: exploiting browser rendering discrepancies

DevFeed: [Fickle PDFs: exploiting browser rendering discrepancies](<https://devfeed.tech/articles/fickle-pdfs-exploiting-browser-rendering-discrepancies-7677.md>)

Original publisher: [Read original article](<https://portswigger.net/research/fickle-pdfs-exploiting-browser-rendering-discrepancies>)

Author: Zakhar Fedotkin

Published: 2024-07-09T12:51:22Z

Content type: article

Language: en

Sources: [PortSwigger Research](<https://devfeed.tech/sources/portswigger-research.md>)

Topics: [pdf](<https://devfeed.tech/topics/pdf.md>), [browsers](<https://devfeed.tech/topics/browsers.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [Firefox](<https://devfeed.tech/topics/firefox.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [apache](<https://devfeed.tech/tags/apache.md>), [article](<https://devfeed.tech/tags/article.md>), [browser](<https://devfeed.tech/tags/browser.md>), [code](<https://devfeed.tech/tags/code.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [google-chrome](<https://devfeed.tech/tags/google-chrome.md>), [java](<https://devfeed.tech/tags/java.md>), [pdf](<https://devfeed.tech/tags/pdf.md>), [research](<https://devfeed.tech/tags/research.md>)

### 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](<https://devfeed.tech/articles/a-preview-of-css-container-queries-28018.md>)

Original publisher: [Read original article](<https://tech.trivago.com/post/2022-02-07-css-container-queries/>)

Author: Kay Drechsler

Published: 2022-02-07T00:00:00Z

Content type: tutorial

Language: en

Sources: [Trivago](<https://devfeed.tech/sources/trivago.md>)

Topics: [container](<https://devfeed.tech/topics/container.md>), [CSS](<https://devfeed.tech/topics/css.md>), [modern web development](<https://devfeed.tech/topics/modern-web-development.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [Chrome](<https://devfeed.tech/topics/chrome.md>), [web-standards](<https://devfeed.tech/topics/web-standards.md>)

Tags: [chrome](<https://devfeed.tech/tags/chrome.md>), [css](<https://devfeed.tech/tags/css.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [google-chrome](<https://devfeed.tech/tags/google-chrome.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [layout](<https://devfeed.tech/tags/layout.md>), [performance](<https://devfeed.tech/tags/performance.md>), [preview](<https://devfeed.tech/tags/preview.md>)

### 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](<https://devfeed.tech/articles/google-chrome-will-soon-let-you-follow-your-favorite-websites-9009.md>)

Original publisher: [Read original article](<https://www.xda-developers.com/chrome-canary-android-experiment-follow-button/>)

Author: Kishan Vyas

Published: 2021-05-19T13:27:37Z

Content type: news

Language: en

Sources: [XDA - RSS](<https://devfeed.tech/sources/xda-rss.md>)

Topics: [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [Chrome Canary](<https://devfeed.tech/topics/chrome-canary.md>), [RSS Feed](<https://devfeed.tech/topics/rss-feed.md>), [Android](<https://devfeed.tech/topics/android.md>), [Google](<https://devfeed.tech/topics/google.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [blog](<https://devfeed.tech/tags/blog.md>), [chrome-canary](<https://devfeed.tech/tags/chrome-canary.md>), [follow](<https://devfeed.tech/tags/follow.md>), [google](<https://devfeed.tech/tags/google.md>), [google-chrome](<https://devfeed.tech/tags/google-chrome.md>), [google-i-o-2021](<https://devfeed.tech/tags/google-i-o-2021.md>), [new-feature](<https://devfeed.tech/tags/new-feature.md>), [rss](<https://devfeed.tech/tags/rss.md>), [xda-news-brief](<https://devfeed.tech/tags/xda-news-brief.md>)

### 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.

## Next.js 9.1.7

DevFeed: [Next.js 9.1.7](<https://devfeed.tech/articles/next-js-9-1-7-3255.md>)

Original publisher: [Read original article](<https://nextjs.org/blog/next-9-1-7>)

Author: Tim Neutkens

Published: 2020-01-06T15:45:00Z

Content type: release

Language: en

Sources: [Next.js Blog](<https://devfeed.tech/sources/next-js-blog.md>)

Topics: [Next.js](<https://devfeed.tech/topics/next-js.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [React](<https://devfeed.tech/topics/react.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>), [Testing](<https://devfeed.tech/topics/testing.md>)

Tags: [cli](<https://devfeed.tech/tags/cli.md>), [google-chrome](<https://devfeed.tech/tags/google-chrome.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [performance](<https://devfeed.tech/tags/performance.md>), [react](<https://devfeed.tech/tags/react.md>), [release](<https://devfeed.tech/tags/release.md>), [testing](<https://devfeed.tech/tags/testing.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### 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](<https://devfeed.tech/articles/unlocalize-google-chrome-omnibar-38382.md>)

Original publisher: [Read original article](<https://meedamian.com/post/unlocalize-google-in-chrome/>)

Author: hi@meedamian.com (Damian Mee)

Published: 2016-01-05T00:00:00Z

Content type: tutorial

Language: en

Sources: [Damian Mee | Blog | Portfolio | About](<https://devfeed.tech/sources/damian-mee-blog-portfolio-about.md>)

Topics: [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [Google](<https://devfeed.tech/topics/google.md>), [Virtual Private Network](<https://devfeed.tech/topics/vpn.md>)

Tags: [change](<https://devfeed.tech/tags/change.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [copy](<https://devfeed.tech/tags/copy.md>), [domain](<https://devfeed.tech/tags/domain.md>), [google](<https://devfeed.tech/tags/google.md>), [google-chrome](<https://devfeed.tech/tags/google-chrome.md>), [search](<https://devfeed.tech/tags/search.md>), [search-engine](<https://devfeed.tech/tags/search-engine.md>), [settings](<https://devfeed.tech/tags/settings.md>), [vpn](<https://devfeed.tech/tags/vpn.md>)

### 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](<https://devfeed.tech/articles/w3c-push-api-crash-course-29160.md>)

Original publisher: [Read original article](<http://tech.zumba.com/2015/05/29/chrome-push-api//>)

Author: Nick Comer (nicholas@zumba.com)

Published: 2015-05-29T00:00:00Z

Content type: tutorial

Language: en

Sources: [Zumba](<https://devfeed.tech/sources/zumba.md>)

Topics: [Chrome](<https://devfeed.tech/topics/chrome.md>), [notifications](<https://devfeed.tech/topics/notifications.md>), [W3C](<https://devfeed.tech/topics/w3c.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [API](<https://devfeed.tech/topics/api.md>), [Google](<https://devfeed.tech/topics/google.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [google-chrome](<https://devfeed.tech/tags/google-chrome.md>), [notifications](<https://devfeed.tech/tags/notifications.md>), [push-notifications](<https://devfeed.tech/tags/push-notifications.md>), [w3c](<https://devfeed.tech/tags/w3c.md>)

### 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](<https://devfeed.tech/articles/fonts-on-fedora-core-19-30650.md>)

Original publisher: [Read original article](<http://bad-concurrency.blogspot.com/2013/10/fonts-on-fedora-core-19.html>)

Author: Michael Barker (noreply@blogger.com)

Published: 2013-10-10T21:13:00Z

Content type: tutorial

Language: en

Sources: [Bad Concurrency](<https://devfeed.tech/sources/bad-concurrency.md>)

Topics: [Fedora](<https://devfeed.tech/topics/fedora.md>), [Font](<https://devfeed.tech/topics/font.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [canonical](<https://devfeed.tech/topics/canonical.md>), [Unity](<https://devfeed.tech/topics/unity.md>)

Tags: [chrome](<https://devfeed.tech/tags/chrome.md>), [fonts](<https://devfeed.tech/tags/fonts.md>), [gnome](<https://devfeed.tech/tags/gnome.md>), [google-chrome](<https://devfeed.tech/tags/google-chrome.md>), [ubuntu](<https://devfeed.tech/tags/ubuntu.md>), [unity](<https://devfeed.tech/tags/unity.md>)

### 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 "

## OS X + ZFS

DevFeed: [OS X + ZFS](<https://devfeed.tech/articles/os-x-zfs-25387.md>)

Original publisher: [Read original article](<https://smileykeith.com/2013/02/21/os-x-plus-zfs/>)

Author: Keith Smiley

Published: 2013-02-21T19:28:00Z

Content type: opinion

Language: en

Sources: [Keith Smiley](<https://devfeed.tech/sources/keith-smiley.md>)

Topics: [Filesystems](<https://devfeed.tech/topics/filesystems.md>), [btrfs](<https://devfeed.tech/topics/btrfs.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [WebKit](<https://devfeed.tech/topics/webkit.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>)

Tags: [btrfs](<https://devfeed.tech/tags/btrfs.md>), [filesystem](<https://devfeed.tech/tags/filesystem.md>), [google](<https://devfeed.tech/tags/google.md>), [google-chrome](<https://devfeed.tech/tags/google-chrome.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [opinion](<https://devfeed.tech/tags/opinion.md>)

### AI overview

The article argues that Apple should replace HFS+ with a modern, openly available filesystem. It recommends adopting BTRFS or an open ZFS port, following the model of WebKit, to encourage broader vendor compatibility, development, and stability.

### Source excerpt

For a long time people have talked about how horrible HFS+ is. Most notably, in my opinion, Linus Torvalds (the creator of Linux and Git) who said "Their file system is complete and utter crap, which is scary." John Siracusa also wrote about the problems with HFS+ in his 10.7 review along with talking about it on his podcast, Hypercritical in episodes 56 and 57. The gist of all this really is that Apple needs a new filesystem. It has been a while since Apple had ZFS support on their website for release in Snow Leopard. After which Apple dropped ZFS support because of licensing issues. There had been talks of Apple developing their own file system, although I think that's the wrong way to go. I think Apple needs to approach file systems the way they approached Safari with Webkit. I think they would be best served by picking up a liberally open source file system, such as BTRFS, or grabbing up one of the ZFS ports and continuing development while leaving it open for anyone to use. One of the great things about this approach is exactly what happened with Webkit and Google Chrome. Google decided to use the Webkit engine to make a product that competes with the main developers of the Webkit project. By doing this with a file system other vendors could use the same implementation and therefore increase development and in turn stability of whichever system was chosen (not to mention compatibility). One thing is for sure. People who understand how integral a file system is want something modern.

## Style sheet for touch devices

DevFeed: [Style sheet for touch devices](<https://devfeed.tech/articles/style-sheet-for-touch-devices-31948.md>)

Original publisher: [Read original article](<https://tech.finn.no2011/03/10/style-sheet-for-touch-devices/>)

Author: gregers

Published: 2011-03-10T13:05:53Z

Content type: tutorial

Language: en

Sources: [Finn.no](<https://devfeed.tech/sources/finn-no.md>)

Topics: [CSS](<https://devfeed.tech/topics/css.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [css](<https://devfeed.tech/tags/css.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [google-chrome](<https://devfeed.tech/tags/google-chrome.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [mobile](<https://devfeed.tech/tags/mobile.md>)

### AI overview

The article explains how to target touch devices with a CSS stylesheet when screen dimensions alone cannot distinguish tablets from desktop displays. It recommends detecting touch support with JavaScript and conditionally writing a stylesheet link before the page becomes visible, while noting limitations in browser touch-event detection.

### Source excerpt

It's easy to include a style sheet for small-screen mobile devices, but what if you specifically want to target touch devices. Then you also need to include devices with larger screens. The iPad has a resolution of 1024x768, but many desktop users also have this resolution, so you can't just increase the max-device-width in your CSS media query. I've tried to find a better solution to the problem, but none seems to exist yet. So the best solution I've found is to use JavaScript to detect if the browser has touch events. It's a bit dangerous because Firefox and Chrome have support for touch, so you can't be sure they don't expose the touch events to devices without a touch screen. Fortunately this has already happened in Google Chrome. The team decided to disable the touch events so the detection developers already used would continue to work. Paul Irish has researched a bit for Modernizr to find out what detection methods work best. You can of course use Modernizr, but if all you need is this test it's not necessary to include the whole library. All you really need is this: 'ontouchstart' in window At first I did the test in the initialization code on document.ready, but then the style sheet will load too late. I definitely don't like document.write in external scripts because then you can't load them asynchronously in an easy manner. However, now it's actually useful, since we want the style sheet to be written out and loaded before the page is visible. <script type="text/javascript"> if("ontouchstart" in window) { document.write('<link rel="stylesheet" type="text/css" media="only screen" href="/css/touch.css">'); } </script> Anyone have a better way?

## 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](<https://devfeed.tech/articles/google-did-something-right-finally-41059.md>)

Original publisher: [Read original article](<https://www.craigkerstiens.com/2008/09/04/Google-did-something-right-.-.-.-.-Finally/>)

Author: Map

Published: 2008-09-05T00:21:56Z

Content type: opinion

Language: en

Sources: [Craig Kerstiens](<https://devfeed.tech/sources/craig-kerstiens.md>)

Topics: [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [Google](<https://devfeed.tech/topics/google.md>), [Firefox](<https://devfeed.tech/topics/firefox.md>), [browser](<https://devfeed.tech/topics/browser.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [google](<https://devfeed.tech/tags/google.md>), [google-chrome](<https://devfeed.tech/tags/google-chrome.md>), [plugins](<https://devfeed.tech/tags/plugins.md>)

### 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.