Possible adjustment to extensions page behavior?

[Matt Frisbie]

In the chrome://extensions page, when the cursor hovers over the extension toggle, this undismissable tooltip message (see screenshot below) shows up and covers all the rest of the buttons for about 3 seconds, making them unclickable. 

As a developer who clicks the covered buttons frequently, this behavior is incredibly annoying. Even a brief mouseover of the toggle button causes the tooltip to show up.

Pushing the tooltip text above the buttons, or make the tooltip click-to-dismiss, or listen for an escape to dismiss, would be a huge improvement.

Thanks!

[DreamBuilder Team]

+1 Confirm the same annoying behaviour!

[Dan Ridd]

Same for us, it's very annoying!!!

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/b8c887d2-cefc-4d28-8c27-eb096a52fe8fn%40chromium.org.

[woxxom]

It's intentional according to https://crbug.com/40279132. Yet another good intention of those that pave the road to hell. I'm pretty biased after seeing ManurefestV3 disastrous handling of user feedback, but hopefully these ideas can be considered:

1. reposition/resize the tooltip to the right or to the top of the switch to match standard behavior of UI tooltips and avoid obscuring the action buttons at the bottom like Details or Reload - our goal of opening the extensions page was to click those buttons;
2. only show the tooltip when "Developer mode" switch is disabled;
3. show the text permanently in the card

[woxxom]

4. make the tooltip disappear when the toggle switch is not hovered - although not a priority for Chromium but this will also match the decades of proper UI/UX design in apps

[woxxom]

So yeah, I don't expect Chrome's UX gurus to admit there are any problems here anytime soon, so I've just patched the binary and removed the tooltip using this simple untip.bat that should be run as admin (don't forget to edit the path to the pak file):

@echo off
set SRC=C:\Program Files (x86)\Google\Chrome\Application\141.0.7390.123\Locales\en-US.pak
chrome-pak-customizer -u "%SRC%" "%temp%\us"
pushd "%temp%\us"
for %%a in (
"This extension may run in the background"
"This extension may read and change site information or run in the background"
) do (
for /f %%b in ('findstr /m /c:%%a *') do (
echo %%b: removed %%a
echo.>%%b
)
)
if not exist "%SRC%.BAK" ren "%SRC%" "*.*.BAK"
chrome-pak-customizer -p pak_index.ini "%SRC%"
popd

pause

[Oliver Dunk]

Hi all,

I definitely find this pretty frustrating too. I don't think anyone would disagree that the current behaviour could be improved.

I'll chat with the team this week and see if we can figure out a way of making it better.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/960b2cfc-4d4b-4d87-85b0-02e595cbf662n%40chromium.org.

[Warren Halderman]

Thanks Oliver, much appreciated.

[Maxim Topciu]

I thought it was only me. Yeah, please fix it.