vivaldi broken on windows 10 surface pro 4 since 16-jun update
-
@aach1 It's not easier to install the new snapshot as standalone? So you don't mess with the working 1.9 every time and you know when a newer version is working for your device
-
@Hadden89 hi - never found myself in this situation before (I've tended to stick to stable releases) so didn't even know that was a possibility. Thanks for the tip and I'll have a look at how to do that.
-
Yes, I've found this as well. I've been using Vivaldi as my default browser for a while now, and mainly use my Surface Pro 4 as a laptop with keyboard attached and often with a wireless mouse. Yesterday I wanted to use it purely as a tablet whilst enjoying some serious sofa time. It was difficult, if not impossible to select items and tabs in Vivaldi. To begin with I thought it was a pen problem and then realised the only app affected was Vivaldi. In the end I was forced to switch to Edge.
-
@Gwen-Dragon I did indeed file a bug report - I mentioned that in the thread but I see I didn't give the number, so apologies for that. It is VB-29544. Contains all the info requested, how to reproduce etc. This doesn't seem to be limited to pro 4, judging by one or two responses in this thread, but it does seem to be limited to pens.
-
@aach1 said in vivaldi broken on windows 10 surface pro 4 since 16-jun update:
I'll have a look at how to do that.
You can install vivaldi (regardless of snapshot or stable) as standalone by clicking on "Advanced" in the install menu --> open the dropdown menu that says "installation type" and select "Install as Standalone" --> select a place where vivaldi should be installed (you can choose whatever you like but I highly recommend not to choose any folder that might interfere with your current "normal" install - just to make sure that nothing gets messed up) --> install.
-
@zaibon thanks for that. It's not very well documented, if I'm not missing something.
-
@aach1 Latest stable release (1.11) does not work on Surface pro 4 (and, judging by other responses here) other pen-based systems. Symptoms remain the same for me at least - a minute or two of reasonable use, then locks up completely and rails the CPU use.
I'm sure I'm not alone in wondering what changed between 1.9 (which still works) and 1.10++ (which don't). Any info welcome.
-
Just to note that this is known to be a Chromium bug. Came up in an unrelated thread.
-
One other thing, because it's not obvious: the fact that this is a Chromium bug doesn't apparently mean that Chrome at more or less the same version will show the same issue. At present, Chrome version 60.0.3112.90 is fine with the Surface pen, Vivaldi 1.11 (60.0.3112.91) is not.
-
@aach1 To be clear, it's not a Chromium issue. It's a Chromium+Vivaldi UI issue.
Chromium has its own native interface. Chrome has its patched "native" interface. Vivaldi has neither. It interacts with the web via a custom-written user interface, which Chromium and Chrome do not share. Touch and pen signals are negotiated by the UI.
Vivaldi does all it can to keep up with the weekly (and MAJOR every six weeks) changes to the underlying Chromium layer. Mapping and coding of touch and pen change with some frequency at the underlying engine layer, but since the authors of Chrome and Chromium are the ones MAKING those changes, they can re-map/re-code their UI to keep up with these changes. No problem. Vivaldi has to discover the changes after the fact, and then make coding changes (sometimes extensive ones) to keep up. So we're at a perpetual disadvantage. But the developers do what they can.
-
@Ayespy thanks for that, very informative, hopefully others reading this thread will get as much from it as I did. Cheers
-
Just as a matter of interest, I downloaded Slimjet (also based on Chromium) to see if it has the same problem. It does. The minute I clicked on a link using the pen, it went into a loop and hung completely.
-
@ayespy thanks for the heads-up on this mate
-
Seeing an update to Chromium 61.0.3163.91 I tested this on Surface pro 4. Still no joy, VB-29544 still applies. V remains unusable on Surface pro 4 at least, and presumably also Surface pro altogether.
-
For morbid interest more than anything, but the Fall Creator's update (1709) of Windows 10 has messed with the Surface pen on many browsers (Chrome, Vivaldi, Firefox and even Edge). V 1.9 is still more or less usable despite this (so I'm sticking with it although it's out of date security-wise) but if any Dev time is going into VB-29544, you might see weirdness (like having to click the button to select text rather than moving the page around). Hopefully this is temporary; enough people are complaining about it...
-
As far as I can see, Version 1.13 has fixed this issue! I've been running it on my surface pro 4 for a few hours now, with lots of the sort of tab activity (selecting tabs with the pen) that would have brought 1.10, 1.11 and (I think) 1.12 to a grinding halt, chewing CPU and not responding. I don't see the fault report (VB-29544) mentioned in the 1.13 release notes, so perhaps the Chromium update just reverted its behaviour to what it was before. Anyway, however it happened, it seems to be fine...
-
@aach1 good for you then!
-
@ian-coog Good for V too, I think. The ability to move the URL and tab bars to the bottom of the browser makes a lot of sense on a touch screen (saves reaching for them). I think V should be really popular on these devices. Devs, if you did this and you're looking in - thanks!
-
out of interest, this morning I installed 1.14.1077.55 (Stable channel) (32-bit) on my surface pro 4, and lo and behold ten hours later I'm still using it and haven't had any of the freezes which I reported in the post. I'd almost given up on this and have been using Firefox quantum happily for a few months. I don't have time to read release notes; can anyone confirm that VB-29544 is considered fixed?
we're not quite there, I should add - gmail labels are still not draggable (and that's a showstopper for me). I'll file a separate one somewhere about that. I note also that when I try to drag a gmail label onto a message, the browser hangs up for a few seconds. Clue, perhaps.
-
@aach1 I didn't noticed VBs around touch inputs but.. I guess chromium/Vivaldi updates are fixing the trouble. Can't answer for gmail labels