3 ms·
> While the new limitations in WebExtensions can be limiting, these in particular don't sound insurmountable. That sounds promising, but I haven't seen anybody
by mikae1 5y ago
> While the new limitations in WebExtensions can be limiting, these in particular don't sound insurmountable.
That sounds promising, but I haven't seen anybody solve it with WebExtensions yet. Just tried Vimium in Chromium too. Same problems.
The end user experience is worse than the picture I painted as my list of drawbacks was incomplete.
Here's another one... Say the server is offline or you mistyped a URL and you get to the "Hmm. We’re having trouble finding that site." page. You're stuck as your vim shortcuts don't work anymore.
It's like a friend that should just be there, but can't be trusted.
- lucideer 5y agoThe "Hmm. We’re having trouble finding that site." page is considered one of the internal protected pages, so in theory toggling the appropriate setting to allow extensions on those pages should fix that issue. Just for clarity, those "special" internal pages in the browser have privileged access to some specific user data, so the intent of having extensions off-by-default on them is to ensure extensions don't all have full access to all that data by default. However, this seems similar to extensions being disabled by default in Private Windows, which is easy to toggle, so I really wish they'd make special browser pages as easy to toggle.