News: 1586221793

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Google tests hiding Chrome extension icons by default, developers definitely not amused by the change

(2020/04/07)


Google is testing a user-interface change that will hide Chrome extensions by default, which is not going down well with developers.

Instead of allowing extension icons to appear one after another to the right of the omnibox – the input box for URLs and search queries – the Chrome Extensions Platform team is trying out a design change that hides the graphical buttons in a menu accessed by a puzzle piece icon.

The test is called the Chrome Extension Toolbar menu and can be enabled from the Chrome Experiments interface, which is accessible by entering chrome://flags/#extensions-toolbar-menu into the omnibox.

"Our goal with this new UI is to make it easier for users to see what extensions can access their data," [1]explained extensions developer advocate Simeon Vincent in a post to the Chromium extensions forum last week.

"When the user clicks the puzzle piece icon, the extension menu opens and displays a list of all enabled extensions the user has installed. The extension list is grouped by the level of data access the extension has on the currently selected tab."

[2]

The current design, on the left, and the proposed jigsaw menu button

Google is in the midst of reworking its Chrome Extension Platform because it is insecure and has been [3]abused by miscreants to steal netizens' information. The point of the Chrome Extension Toolbar experiment is to make the privacy implications of extensions, and the permissions they request, more visible to users.

But if this particular change gets adopted, Chrome extensions themselves will become less visible, upending developers' expectations for how users will interact with their code.

Users will be able to "pin" extension icons so they remain visible and available for interaction, but they have to choose to do so upon installation. That's the opposite of the behavior in Chrome 80, the current stable version of Google's browser, where extension icons get pinned by default. Developers of extensions thus can no longer assume that users will be able to engage with their code.

Vincent has advised those who make extensions to rethink user interaction.

"If your extension's action button is a key component of your experience, consider updating your onboarding flow to encourage users to pin the extension to their toolbars," he said.

[4]

New design being tested for Chrome Extensions Toolbar menu ... Click to enlarge

Many of those who have created Chrome extensions assumed users would be able to access extension features directly from the Chrome browser bar by clicking on the displayed extension control. Among those commenting on the change in the Chromium extensions forum, most expressed opposition to the altered interface and on-boarding experience.

"This seems like a huge misstep," [5]wrote Robert James Gabriel, founder of Helperbird, an accessibility extension. "I deal with a lot of kids and schools with my business. Ninety-nine percent will not pin unless we can do it on install."

The risk for programmers is that extensions hidden by default will be forgotten.

"I completely agree with everyone else's sentiment, hiding icons by default seems like a terrible user experience and will cause many more issues than it fixes," [6]wrote Evan Carothers, founder of recruiting and sales extension ZapInfo. "The excuse of keeping the UI uncluttered makes no sense considering the users are opting to install these extensions."

Carothers argued it would be better to continue pinning extensions by default and to provide users with an option to unpin if they really can't deal with the clutter. To do otherwise, he contended, will limit extension usage and adoption.

Chrome extension makers, however, may have to get used to a shorter leash. Anticipating how Google's security and privacy-focused platform changes will prompt extension users to be more cautious in granting access permissions, Vincent said developers should plan for more restrictions. "Be prepared for your extension to not have the host permissions you expect," he said. ®

Sponsored: [7]Choosing A Low-Code Vendor



[1] https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/rOso__zU_sM/2kUkcjFxAgAJ

[2] https://regmedia.co.uk/2020/04/06/chrome_extension_menu_experiment.png

[3] https://www.theregister.co.uk/2020/02/14/500_chrome_extensions_removed/

[4] https://regmedia.co.uk/2020/04/06/chrome_extension_menu_experiment_default.jpg

[5] https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/rOso__zU_sM/GxvNLPNHBwAJ

[6] https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/rOso__zU_sM/VqAATvy9BwAJ

[7] https://go.theregister.co.uk/tl/1936/-8579/choosing-a-low-code-vendor?td=wptl1936

When will they learn?

Anonymous Coward

Pissing off the developers whom write mods for your software that extends functionality, enables bits you may have never considered, and allows the user of your product to do the things they need to do rather than the things you think they need to do is a great way to cause those developers to leave for greener pastures.

Those developers go to your competition, the people using your product start leaving for companies that offer the things they need (rather than the ones you think they need), and you quickly become just another Microsoft swirling the toilet bowl of fail.

Hey Google! Remember when your motto used to be "Don't Be Evil"? Why do you insist on making MS look good in comparison?

Re: When will they learn?

Foxglove

Some valid points AC, but...

Where are the 'Greener Pastures' of which you speak? Chrome is very popular.

'Those developers go to your competition' Again, Chrome is very popular.

'Microsoft swirling the toilet bowl of fail.' MS seem to be doing OK, not anywhere near the outfall as far as I can see.

'Don't Be Evil' Old news, not even worth mentioning these days. Sorry for mentioning it.

At least with Chrome you can see which extensions are installed.

For example IE can hide an extension from the user so you don't even know it is installed.

Snow Software being an example, that is legit software but it is an example of a user being denied access to view what is going on in their browser. Fine, install it and restrict use but don't allow hiding it.

There is only one valid reason for hiding extensions from the user, and that is nefarious activity.

If your employer wants to install stuff you can't tamper with that 's OK, but things should never be completely hidden from the user.

Now avoiding Chrome everywhere

Sleep deprived

For me, Manifest v3 was the turning point. Before that, when I had a problem rendering a page with Firefox, I'd launch Chrome, sometimes with success. Now, I do everything I can to avoid Chrome, both under Windows and Android, instead trying to fix the problem with Firefox, eventually sending them a report with URL and relevant data. Google has become a despicable software publisher with every move making the attached strings ever less subtle.

cornetman

So Google wants to make users more aware of what extensions are doing...by hiding them?

Anyone who thinks UNIX is intuitive should be forced to write 5000 lines of
code using nothing but vi or emacs. AAAAACK!
(Discussion in comp.os.linux.misc on the intuitiveness of commands, especially
Emacs.)