Please consider removing the limitation of chrome:// url.
-
Extensions like https://github.com/1995eaton/chromium-vim/issues/53 will be more powerful and consistent if they can be activated in pages with url chrome://
-
@amosbird: Ultimately, that will not be a valid internal url for Vivaldi in most cases. All such pages will be vivaldi://. Already, though, functions which were broken on some internal pages have been added or enabled. I expect that to continue.
-
@Ayespy oh, do you mean that vivaldi will not be constraint by such limitation?
-
@amosbird: Seems it will get better and better that way. Exceptions will have to be written for each internal page, as the Vivaldi internal pages replace the Chromium ones, because internal pages aren't real web pages. They just look that way. But, yeah. Over time, I expect the limitation to become less relevant.
-
@Ayespy That's great. Can't wait to see it happen
-
@Ayespy um, vivaldi's built-in one key hotkey also doesn't work in pdf tabs.
-
@amosbird: Please start a topic under your OS for that.
-