View page source not always works
I'm not sure if this is a bug or the way browser was developed to work, but I find view source code (or simply CTRL+U) not always works. If some page auto "focuses" mouse pointer on form's input field right after loading, CTRL+U doesn't work. The workaround is to manually move mouse pointer outside the form, left-click, and then CTRL+U starts working again.
You can reproduce it easily (even if page doesn't focus pointed on form) - go to any page that has form, click on any field in the form, and try using CTRL+U - it won't work. As soon as you move mouse outside the form (don't forget to click some empty space), viewing source becomes available again.
It is not passed to show the source in input and teaxtarea fields. Why? The Ctrl U may be used as Underline command by webmail/forum/blog/etc. editors.
Makes some sense, but it's very weird, as I don't know any other browser which blocks viewing source when mouse pointer is focused on forms...
I don't know any other browser which blocks viewing source when mouse pointer is focused on forms...
I can tell you: the keyboard interaction of UI and webpage in Vivaldi is slightly different from your "other" browsers.
And the Vivaldi developers had to do it like this as previously shortcuts were not correctly routed to webapps.
@Gwen-Dragon Clearly it requires a more sophisticated workaround than just disabling all (or most) of the keyboard shortcuts whenever an input field is focused. If other browsers (I checked Opera 42) can do that, then Vivaldi could do that too... 😉
I see it as a normal behaviour, if input/text fields are focused, the vivaldi ui shortcuts should not be triggered, but instead act as they should in a text field, many complained already when Vivaldi reacted on backspace or other ctrl-key shortcuts even if text field is in focus, so it's better it stays this way.
@iAN-CooG I disagree. The "common" keyboard shortcuts (like backspace, CTRL+Z etc.) shouldn't perform any browser actions when the input field is focused - that's true. But any "unusual" shortcuts (like CTRL+U for example) shouldn't be arbitrarily disabled if they're not assigned any action by the website. IMO disabling all shortcuts is the easiest and at the same time the worst possible solution - it's just throwing the baby out with the bathwater.
We can agree to disagree, but I see it as more of a problem if it would react where it shouldn't. Nobody is going to die if to get the ctrl-key shortcut working mouse or tab to unfocus the text field has to be pushed. If Vivaldi Team can even provide a working solution, the better, as of now I'm ok if it stays like this.
I see a possible fix can be applied super easily: if such a shortcut is "reserved" for visual text editors to underline text, browser can simply check if this field is textarea or not. If it's textarea, shortcut can remain reserved. If it's input, view source should start working (because all the visual editors I saw only use textareas).
I see a possible fix can be applied super easily:
Please report this as a feature wish or bug.
How to do a bugreport for Vivaldi
Report the bug at https://vivaldi.com/bugreport/
Describe the issue as precise as you can.
If you use any extensions please give information which ones you use.
If you have a URL or a own testpage which can checked, add it to the bugreport.
If you have own testcase files (HTML, CSS, JS etc.) add them to the confirmation mail you get after report.
If you have a screenrecording video, you can attach it to give the developers a hint how this might happen or look like.
You will get a bug confirmation mail and in a reply to this mail you can add more information and files as attachments for the testers and bug tracking team.
Thanks in advance for helping us to make Vivaldi better!