Downloading Chrome using Microsoft Edge is already a nightmare filled with banners and stop-gaps, and nothing seems to be stopping Microsoft from adding even more. From a report: Last weekend, we noticed that an attempt to download Google Chrome using Microsoft Edge results in the latter opening its sidebar with a poll, asking you to explain to Microsoft how you could dare try downloading Google Chrome. Of course, the exact wording is more tame, but you get the idea. Now, besides dismissing several banners and a full-size ad injected on the Chrome website, Edge wants you to answer a questionnaire with the following options:

We love having you! Can you please take a minute to tell us why you are trying another browser?

I can't search Google easily
I can't access my Google documents
I don't have my favorites or passwords here
Too many ads and pop-ups
I don't like the news feed
It's too slow
My websites don't work on Microsoft Edge
My reason is not listed

Google is getting ready to test a new "IP Protection" feature for the Chrome browser that enhances users' privacy by masking their IP addresses using proxy servers. From a report: Recognizing the potential misuse of IP addresses for covert tracking, Google seeks to strike a balance between ensuring users' privacy and the essential functionalities of the web. IP addresses allow websites and online services to track activities across websites, thereby facilitating the creation of persistent user profiles. This poses significant privacy concerns as, unlike third-party cookies, users currently lack a direct way to evade such covert tracking.

While IP addresses are potential vectors for tracking, they are also indispensable for critical web functionalities like routing traffic, fraud prevention, and other vital network tasks. The "IP Protection" solution addresses this dual role by routing third-party traffic from specific domains through proxies, making users' IP addresses invisible to those domains. As the ecosystem evolves, so will IP Protection, adapting to continue safeguarding users from cross-site tracking and adding additional domains to the proxied traffic. "Chrome is reintroducing a proposal to protect users against cross-site tracking via IP addresses. This proposal is a privacy proxy that anonymizes IP addresses for qualifying traffic as described above," reads a description of the IP Protection feature. Initially, IP Protection will be an opt-in feature, ensuring users have control over their privacy and letting Google monitor behavior trends.

Google is making a few changes to the way its search and address bar -- known as the omnibox -- works in the Chrome browser. The changes are individually pretty small, but there's an important and somewhat unexpected trend in them all: Google is making it easier for you to move around the web without having to do so many Google searches. From a report: If you're in Chrome on desktop or mobile, the browser will now try and correct your URL typos, so when you type thevrege.com or ninteendo.com, you'll get autocomplete suggestions based on the right site and not whatever is behind those misspelled domains. The omnibox's autocomplete will now be smarter in general, predicting the site you're looking for based on keywords rather than just guessing what URL you're typing. Chrome can also now search within your bookmarks for sites and files related to what you're typing.

All those features are based on your own browsing history and bookmarks, so it's just Chrome becoming slightly more personalized. But the last change is web-wide and is pretty off-brand for Google: when you start to type in the name of a popular website, the omnibox will show that site's URL in the list of suggestions, and you can select it to go right to that site. (You might have seen this one already: it's been rolling out for a couple of weeks and should be live to everyone now.)

Google has introduced Chromebook Plus, a new certification that's meant to help shoppers identify high-quality Chromebooks to buy. From a report: Much like Intel's Evo program for Windows PCs, the Chromebook Plus branding will be awarded to laptops that meet a set of minimum requirements. The idea is that even a shopper who's not familiar with PC specs can see the "Chromebook Plus" label on a product and be assured that Google thinks it's a good product. Chromebook Plus devices must have:

An Intel Core (i3 or higher) or AMD Ryzen 7000 CPU
An IPS panel with at least 1080p resolution
A 1080p webcam
8GB of RAM
128GB of storage

There's an interesting absence here: battery life. In fact, the phrase "battery life" does not appear once in Google's press release. Curious! I asked Google spokesperson Peter Du about this, and he provided the following statement: "All Chromebooks are required to meet a 10 hours battery life requirement based on internal testing standards. While not a new requirement for Chromebook Plus like the 1080p screen or 8GB of RAM, Chromebook Plus laptops must also adhere to this."

Long-time Slashdot reader Tablizer writes: Chrome's spell checker doesn't list the proper option for "devine" or "preditor". Soundex would match them and is relatively simple to implement, but most browsers allegedly use the Hunspell algorithm. However, Hunspell doesn't handle incorrect vowels well.

Browsers could offer a "More spelling options" menu item to bring up a wider dialog using alternative algorithms, such as Soundex. Until then, can anyone recommend good spelling plugins?

An anonymous reader quotes a report from Ars Technica: GPUs from all six of the major suppliers are vulnerable to a newly discovered attack that allows malicious websites to read the usernames, passwords, and other sensitive visual data displayed by other websites, researchers have demonstrated in a paper (PDF) published Tuesday. The cross-origin attack allows a malicious website from one domain -- say, example.com -- to effectively read the pixels displayed by a website from example.org, or another different domain. Attackers can then reconstruct them in a way that allows them to view the words or images displayed by the latter site. This leakage violates a critical security principle that forms one of the most fundamental security boundaries safeguarding the Internet. Known as the same origin policy, it mandates that content hosted on one website domain be isolated from all other website domains. [...]

GPU.zip works only when the malicious attacker website is loaded into Chrome or Edge. The reason: For the attack to work, the browser must:

1. allow cross-origin iframes to be loaded with cookies
2. allow rendering SVG filters on iframes and
3. delegate rendering tasks to the GPU

For now, GPU.zip is more of a curiosity than a real threat, but that assumes that Web developers properly restrict sensitive pages from being embedded by cross-origin websites. End users who want to check if a page has such restrictions in place should look for the X-Frame-Options or Content-Security-Policy headers in the source. "This is impactful research on how hardware works," a Google representative said in a statement. "Widely adopted headers can prevent sites from being embedded, which prevents this attack, and sites using the default SameSite=Lax cookie behavior receive significant mitigation against personalized data being leaked. These protections, along with the difficulty and time required to exploit this behavior, significantly mitigate the threat to everyday users. We are in communication and are actively engaging with the reporting researchers. We are always looking to further improve protections for Chrome users."

An Intel representative, meanwhile, said that the chipmaker has "assessed the researcher findings that were provided and determined the root cause is not in our GPUs but in third-party software." A Qualcomm representative said "the issue isn't in our threat model as it more directly affects the browser and can be resolved by the browser application if warranted, so no changes are currently planned." Apple, Nvidia, AMD, and ARM didn't comment on the findings.

An informational write-up of the findings can be found here.

An anonymous reader quotes a report from Reuters: The U.S. Justice Department on Monday objected to removing the public from the court during some discussions of how Google prices online advertising, one of the issues at the heart of the antitrust trial under way in Washington. The government is seeking to show that Alphabet's Google broke antitrust law to maintain its dominance in online search. The search dominance led to fast-increasing advertising revenues that made Google a $1 trillion company. [Throughout the trial, Google's defense is that its high market share reflects the quality of its product rather than any illegal actions to build monopolies in some aspects of its business.]

David Dahlquist, speaking for the government, pointed to a document that was redacted that had a short back and forth about Google's pricing for search advertising. Dahlquist then argued to Judge Amit Mehta, who will decide the case, that information like the tidbit in the document should not be redacted. "This satisfies public interest because it's at the core of the DOJ case against Google," he said. Speaking for Google, John Schmidtlein urged that all discussions of pricing be in a closed session, which means the public and reporters must leave the courtroom. [...]

Case in point was testimony given early Monday by a Verizon executive, Brian Higgins, about the company's decision to always pre-install Google's Chrome browser with Google search on its mobile phones. After about 30 minutes of testimony, Higgins' testimony was closed for the next two hours. It's possible that he was asked about Google's payments to Verizon but the public will never know. Those payments -- which the government said are $10 billion annually to mobile carriers and others -- helped the California-based tech giant win powerful default positions on smartphones and elsewhere.

Google is working to push back the expiration date of Chromebooks, addressing concerns held by school administrators that the laptops are too short-lived to be cost effective. From a report: The Alphabet-owned company -- which develops the Chrome operating system running on computers made mostly by others -- said Thursday it plans to provide software updates for Chromebooks for up to a decade. The new policy, which starts next year, ensures that no existing Chromebook will expire within the next two years. The disclosure of this policy change comes after an August column in The Wall Street Journal detailing schools' struggles with expiring Chromebooks. Chromebooks are ubiquitous in classrooms around the country, but some education software doesn't work after what Google calls the Auto Update Expiration date. Unsupported Chromebooks can't be used for mandatory state testing, even if the hardware still appears functional.

When the laptops expire, school districts recycle them, sometimes at a cost, and spend millions of dollars on replacements. Google currently sets expiration dates based on the release date of specific models. Newer models have eight years of support, while older Chromebooks have five. Starting in 2024, Google will support a given laptop "platform" -- a certain combination of hardware components -- for 10 years after the first device in the platform hits store shelves. These so-called platforms aren't unique to specific brands or manufacturers and can be found in a variety of distinct models.

An anonymous reader quotes a report from Gizmodo: Google's Privacy Sandbox, a controversial set of tools and settings meant to replace third-party cookies, is now on almost every single Chrome browser, according to a company blog post published Thursday. Google says Privacy Sandbox is now available to around 97% of Chrome users, and that number will reach 100% in the next few months. The news comes on the heels of the browser's 15th anniversary, which Google is celebrating by redesigning Chrome to make it look and feel more closely aligned with the design paradigm of Android and the rest of the Google suite. The final step in this process comes in 2024, when Google will disable third-party cookies in Chrome for good, marking the end of their decades-long reign of privacy-violating terror.

Back in 2019, Google said the cookie era was coming to a close. In place of third-party cookies, Privacy Sandbox will implement a long list of new tools for the ad industry. Google, after all, makes all of its money by spying on you and turning the insights into ads, so it's not about to put itself out of business. In fairness, this new system is really more private, though it's private on Google's terms. The biggest change is "Ad Topics," a.k.a. the Topics API if you're a huge nerd who's been following this stuff for years. With Topics, Chrome will keep track of all the websites you're looking at and sort you into a variety of categories. This tracking happens in your browser and the data stays on your device. Neither Google nor anyone else gets to see your browsing history or learn anything about you as an individual throughout this process. Websites and advertising companies will know there's a person interested in a certain Topic, but they won't be able to tell who you are specifically.

There's also an extremely complicated technique websites can use to tag you with subjects they want you to see ads about, called "Site Suggested Ads." Google is also rolling out a tool called "Ad Measurement," which helps companies keep track of how well their ads are working through metrics such as the time of day you saw an ad and whether you clicked on it. Google gives users some control over how these tools are implemented. With the rollout of Privacy Sandbox comes new settings listed as "Ad privacy controls," which you can adjust in Chrome's preferences. Further reading: Chrome is About To Look a Bit Different

Chrome on the desktop is about to get a new look. From a report: Google's widely used browser is getting an update based on its Material You design language in the coming weeks, and in this case, that will include refreshed icons with "a focus on legibility" and new color palettes that "better complement your tabs and toolbar," according to a blog post from Chrome VP Parisa Tabriz.

To date, Google has processed more than seven billion copyright takedown requests for its search engine. The majority of the reported links are purged from Google's search index, as required by the DMCA. Recently, however, Google appears to gone a step further, using search takedowns to "moderate" users' privately saved links collections. TorrentFreak: A few hours ago, Eddie Roosenmaallen shared an email from Google, notifying him that a link had been removed from his Google Saved collection because it violates Google's policy. The reason cited for the removal is the "downstream impact," as the URL in question is "blocked by Google Search."

"The following saved item in one of your collections was determined to violate Google's policy. As a result, the item will be moderated..," Google writes, pointing out a defunct KickassTorrents domain as the problem. Initially, it was suggested that this removal impacted Google's synched Chrome bookmarks but further research reveals that's not the case. Instead, the removals apply to Google's saved feature. This Google service allows users to save and organize links, similar to what Pinterest does. These link collections can be private or shared with third parties.

The latest version of the flagship FOSS browser is out, and it's picked up one of the main features for which we keep Chrome around. From a report: The Firefox version 117 feature list might not look all that impressive, but it does have a big-ticket feature that may tempt people back: automatic translation. The snag is it's disabled by default in the release version, and you'll have to manually enable it. Although it was enabled in the betas, Mozilla has decided to go for a staged rollout and not enable it for everyone until Firefox 118 in six weeks or so.

The new feature is integrated, privacy-respecting machine translation between multiple languages. This was already possible in older versions, but it needed an extension, and that had two side effects. One is that the extension hooked deep into the core of the browser in ways that Mozilla wasn't comfortable about, and the other is that once your text had been sent out to a third-party website, it could be snooped upon -- but the victims of any snooping would blame the browser, even if it wasn't the browser's fault. To enable it, go to the configuration page (enter about:config in the address bar), and search for a setting called browser.translations.enable.

An anonymous reader writes: I thought I had malware on my main Windows 11 machine this weekend. There I was minding my own business in Chrome before tabbing back to a game and wham a pop-up appeared asking me to switch my default search engine to Microsoft Bing in Chrome. Stunningly, Microsoft now thinks it's ok to shove a pop-up in my face above my apps and games just because I dare to use Chrome instead of Microsoft Edge. This isn't a normal notification, either. It didn't appear in the notification center in Windows 11, nor is it connected to the part of Windows 11 that suggests new features to you. It's quite literally a rogue executable file that has somehow appeared in c:\windows\temp\mubstemp and is digitally signed by Microsoft.

"We are aware of these reports and have paused this notification while we investigate and take appropriate action to address this unintended behavior," says Caitlin Roulston, director of communications, in a statement to The Verge. [...] This isn't Microsoft's first rodeo, either. I'm growing increasingly frustrated by the company's methods of getting people to switch from Google and Chrome to Bing and Edge. Microsoft has been using a variety of prompts for years now, with pop-ups appearing inside Chrome, on the Windows taskbar, and elsewhere. Microsoft has even forced people into Edge after a Windows Update, and regularly presents a full-screen message to switch to Bing and Edge after updates.

Google Chrome is adding a read-aloud option to its reading mode, allowing users to have articles read to them like an audiobook. Android Police reports: Google is actively working to bring additional features to its reading mode, and a handy read-aloud option is already on the way for the Chrome browser. As the name suggests, read aloud basically reads out the entire article, as if you're listening to an audiobook, with text-to-speech (TTS) capabilities. Again, a few mainstream browsers and apps like Pocket already have the feature, but Google Chrome is only now rolling it out through the Canary channel.

When you open an article in Chrome Canary's reading mode on the desktop, you will see a new option, as spotted by browser expert Leopeva64. You can use this tiny play button to get the browser to read the article aloud for you. In the video sample shared by the user, you can hear what the narration sounds like -- and it isn't very pleasing. The voice output sounds pretty robotic as it used to be in the early days of TTS conversions, which is especially ironic coming from Google, which has some of the most natural-sounding voice models at its disposal. This clearly indicates that the read-aloud feature is in its early stages of development and will take some time before it becomes ready for prime time.

An anonymous reader quotes a report from 9to5Google: Google has worked with Cameyo to give enterprise Chromebooks another way to run Windows applications using ChromeOS Virtual App Delivery. Cameyo is an enterprise company that offers a "Virtual App Delivery" (VAD) platform that can stream Windows, Linux, internal web, and SaaS applications to other devices. This offering is now getting tight integration with ChromeOS. These Windows apps appear like other icons in a Chromebook's launcher and taskbar. Behind the scenes, they are PWAs (Progressive Web Apps) that aim to blur their streamed nature with native file system integration. This includes letting users access local files and folders from within the virtual instances. Similarly, integration with the ChromeOS Clipboard Connector allows for local copy and paste.

When a user opens a specific file type, Cameyo makes it so that the appropriate virtual app launches. These virtual apps can be streamed from the cloud or on-premises data centers. Compared to full virtual desktop apps, this approach is said to "eliminate the infrastructure and licensing complexity." On the security front: "apps and devices are isolated from network resources and segmented by default so that users only access the apps and data they need to get their jobs done, all while eliminating the need to expose firewall and server ports to the open internet." ChromeOS Virtual App Delivery with Cameyo is available today as an enterprise offering. There is no consumer equivalent.

Mozilla has implemented the WebExtensions system in its browser, allowing Firefox users to import select extensions from other browsers like Chrome. gHacks reports: The feature, which is in testing at the moment, can be enabled by all users of the latest stable version of Firefox.

1. Load about:config in the browser's address bar.
2. Confirm that you will be careful to continue.
3. Search for browser.migrate.chrome.extensions.enabled.
4. Set the feature to True, which enables it.
5. Restart Firefox.

Mozilla has integrated it into the browser's import functionality, which users may use on first run or at any time from the Settings page. To do so, select Menu > Settings > Import Data (button), or load about:preferences#general in the browser's address bar and activate the import data button on the page. Select Chrome from the list, expand the available import options and make sure extensions are checked. Imports are usually limited to some data, such as bookmarks or the browsing history. Firefox is the first major browser, maybe the first browser at all, that adds extensions to the list of supported imports.

The feature is limited at the time to Google Chrome and select extensions. Even though Firefox and Chrome extensions use the same framework, WebExtensions, they are not compatible immediately. Firefox users who attempt to install extensions from Chrome's Web Store may notice that this is not working. Mozilla decided to create a list of extension pairs for extensions that are available on the Chrome Web Store and the Mozilla Add-ons Store. Instead of importing the Chrome extension directly, Firefox is installing the Firefox version of the extension from Mozilla's own extension store.

Google is testing a new feature in the Chrome browser that will warn users when an installed extension has been removed from the Chrome Web Store, usually indicative of it being malware. BleepingComputer reports: An unending supply of unwanted browser extensions is published on the Chrome Web Store and promoted through popup and redirect ads. These extensions are made by scam companies and threat actors who use them to inject advertisements, track your search history, redirect you to affiliate pages, or in more severe cases, steal your Gmail emails and Facebook accounts. The problem is that these extensions are churned out quickly, with the developers releasing new ones just as Google removes old ones from the Chrome Web Store. Unfortunately, if you installed one of these extensions, they will still be installed in your browser, even after Google detects them as malware and removes them from the store.

Due to this, Google is now bringing its Safety Check feature to browser extensions, warning Chrome users when an extension has been detected as malware or removed from the store and that they should be uninstalled from the browser. This feature will go live in Chrome 117, but you can now test it in Chrome 116 by enabling the browser's experimental 'Extensions Module in Safety Check' feature. [...] Google says that extensions can be removed from the Chrome Web Store because they were unpublished by the developer, violated policies, or were detected as malware.

Michael Larabel writes via Phoronix: Mozilla developers are celebrating that they are now faster than Google Chrome with the SunSpider JavaScript benchmark, although that test has been superseded by the JetStream benchmark. Last week a new Firefox Nightly News was published that outlines that "We're now apparently beating Chrome on the SunSpider JavaScript benchmark!" The provided numbers now show Firefox easily beating Chrome in this decade-old JavaScript benchmark. The benchmarks come from AreWeFastYet.com. Meanwhile for the newer and more demanding JetStream 2.0 benchmark, Google Chrome continues to win easily over Firefox. You can learn more about the latest Firefox Nightly build advancements via Firefox Nightly News.

Google's AI-powered Search Generative Experience (SGE) is getting a major new feature: it will be able to summarize articles you're reading on the web, according to a Google blog post. From a report: SGE can already summarize search results for you so that you don't have to scroll forever to find what you're looking for, and this new feature is designed to take that further by helping you out after you've actually clicked a link. You probably won't see this feature, which Google is calling "SGE while browsing," right away. Google says it's a new feature that's starting to roll out Tuesday as "an early experiment" in its opt-in Search Labs program. (You'll get access to it if you already opted in to SGE, but if you haven't, you can opt in to the feature on its own.) It will be available first in the Google app on Android and iOS, and the company is bringing it to the Chrome browser on desktop "in the days ahead."

OS News' managing editor calls Firefox "the single most important desktop Linux application," shipping in most distros (with some users later opting for a post-installation download of Chrome).

But "I'm genuinely worried about the state of browsers on Linux, and the future of Firefox on Linux in particular..." While both GNOME and KDE nominally invest in their own two browsers, GNOME Web and Falkon, their uptake is limited and releases few and far between. For instance, none of the major Linux distributions ship GNOME Web as their default browser, and it lacks many of the features users come to expect from a browser. Falkon, meanwhile, is updated only sporadically, often going years between releases. Worse yet, Falkon uses Chromium through QtWebEngine, and GNOME Web uses WebKit (which are updated separately from the browser, so browser releases are not always a solid metric!), so both are dependent on the goodwill of two of the most ruthless corporations in the world, Google and Apple respectively.

Even Firefox itself, even though it's clearly the browser of choice of distributions and Linux users alike, does not consider Linux a first-tier platform. Firefox is first and foremost a Windows browser, followed by macOS second, and Linux third. The love the Linux world has for Firefox is not reciprocated by Mozilla in the same way, and this shows in various places where issues fixed and addressed on the Windows side are ignored on the Linux side for years or longer. The best and most visible example of that is hardware video acceleration. This feature has been a default part of the Windows version since forever, but it wasn't enabled by default for Linux until Firefox 115, released only in early July 2023. Even then, the feature is only enabled by default for users of Intel graphics — AMD and Nvidia users need not apply. This lack of video acceleration was — and for AMD and Nvidia users, still is — a major contributing factor to Linux battery life on laptops taking a serious hit compared to their Windows counterparts... It's not just hardware accelerated video decoding. Gesture support has taken much longer to arrive on the Linux version than it did on the Windows version — things like using swipes to go back and forward, or pinch to zoom on images...

I don't see anyone talking about this problem, or planning for the eventual possible demise of Firefox, what that would mean for the Linux desktop, and how it can be avoided or mitigated. In an ideal world, the major stakeholders of the Linux desktop — KDE, GNOME, the various major distributions — would get together and seriously consider a plan of action. The best possible solution, in my view, would be to fork one of the major browser engines (or pick one and significantly invest in it), and modify this engine and tailor it specifically for the Linux desktop. Stop living off the scraps and leftovers thrown across the fence from Windows and macOS browser makers, and focus entirely on making a browser engine that is optimised fully for Linux, its graphics stack, and its desktops. Have the major stakeholders work together on a Linux-first — or even Linux-only — browser engine, leaving the graphical front-end to the various toolkits and desktop environments....

I think it's highly irresponsible of the various prominent players in the desktop Linux community, from GNOME to KDE, from Ubuntu to Fedora, to seemingly have absolutely zero contingency plans for when Firefox enshittifies or dies...