Why does every release by the Opera devs refuse to honor the taskbar autohide/show convention?
-
Enter Fullscreen mode, then close it. This is guaranteed to cause the problem in Opera 12.17.
I have seen it in Vivaldi too, but as I said it's very easy to fix. Just press the Windows key to show the task bar.
-
Enter Fullscreen mode, then close it. This is guaranteed to cause the problem in Opera 12.17.
No, just tried, O12 is still working perfectly for me (o12.17 x64 on win 8.1 x64)
Just guessing…. Maybe something related to HW acceleration and so VGA driver dependent ?
-
Pesala wrote:
Enter Fullscreen mode, then close it. This is guaranteed to cause the problem in Opera 12.17.That's not the case with me, just tried it. I had more problems with auto-hide taskbar with Opera Blink, it seemed to be a random thing even then, perhaps it depends on the OS. Clicking on the Windows key takes one to the Start Page with Win 8.1.
-
Clicking on the Windows key takes one to the Start Page with Win 8.1.
Not for most of the people who use it.
Never heard about classic shell, startisback and so on ?
-
Pesala wrote:
Enter Fullscreen mode, then close it. This is guaranteed to cause the problem in Opera 12.17.That's not the case with me, just tried it. I had more problems with auto-hide taskbar with Opera Blink, it seemed to be a random thing even then, perhaps it depends on the OS. Clicking on the Windows key takes one to the Start Page with Win 8.1.
Not here. But then I have Classic Shell installed.
-
First of all, while Vivaldi and Opera are technically two entities, the staff and design teams have a lot of overlap. Vivaldi is founded by the founder of Opera and brought staff over.
Second, I'm not insulting anyone, I'm bringing attention to a persistent issue because I believe that they are miles ahead of Mozilla and Microsoft and its design flaws like this that prevent them from gaining market traction that they so richly deserve. It's a quirk that significantly changes how things work in terms of daily function and like Windows 8 that spells a quick death on growth in IT departments in corporate environments, and its this demographic that casts a disproportionate shadow on market growth and growth potential. You fail there, your browser is destined for decimal to single digit percentiles. It's just how it goes.For me, on Windows 7 x64, Windows 8 x64, and Windows 10 x64, hitting the start menu key does not solve the problem, and it never did in Opera either. It shows the taskbar briefly but the behavior persists.
This was eventually fixed in Opera but it took them literally two years. It's not an engineering hurdle, it's an easy fix. Browser should not be overriding the essential operating system functions. No other browser functions this way because it is obstructive to multitasking and productivity oriented use. -
@ The_Solutor & Ayespy
I've heard of Classic Shell and the like but never really considered them, I've just taken a look, perhaps I should have checked it out before, never been keen on that Start Page.
-
@ The_Solutor & Ayespy
I've heard of Classic Shell and the like but never really considered them, I've just taken a look, perhaps I should have checked it out before, never been keen on that Start Page.
I Started to use Classic Shell well before Win 8 was even mentioned somewhere.
Mainly because is way more configurable than the stock vista/seven start menu.
I like the functions of Win7 menu but I prefer to have the cascading all programs section.
Also, with classic shell, I can have the reboot button even on remote sessions, which is very important for me.
-
Without Classic Shell, I don't think I could use Windows 8. It is a UI which seems to be specifically designed to keep one from getting anything done.
-
I've encountered problems with the taskbar not showing when set to autohide with pretty much every Chromium-based browser at some point. And last I've heard, it's supposed to actually be a Chromium bug.
-
It's an opera bug. Appeared sometime in 2013 iirc, and not fixed until
http://blogs.opera.com/desktop/changelog23/#b1522.75I've never seen it in another browser but it looks like for a short while Chrome had this bug as well.
If it is a chromium bug, this wouldn't still be happening because this is not an issue anymore outside of Vivaldi. Unless maybe they are building on an old base?For those not seeing the bug, are you running in a maximized window?
-
What do you mean "it's an Opera bug"? If it was an Opera bug, how would it be relevant in any way to Vivaldi? Vivaldi is not Opera, they don't share bugs (unless it's a bug affecting the Blink engine in general).
Also when I say that I've encountered this problem, what I mean is closer to "one in hundred times I've ran that browser, I've seen that happen". Including Vivaldi. Currently tested it in both Win 7 x64 and Win 8.1 x64, taskbar on autohide, maximized browser Window and no problems whatsoever.
-
They share a code base and are developed by many of the same people… and a bug that has been fixed in Opera after the split shows up in Vivaldi...
I'm using Windows 10 and it occurs 100% of the time the window is maximized. It happens as well on 7 and 8 but I did not do any focused testing so I can't say how often or under what circumstances it is replicable there. Just noticed that it was happening. -
I'm running Windows 7, and I almost always only have the window maximized. I've never once had this problem with Vivaldi, and I cannot remember ever having it with Opera. I have had this problem with Sleipnir and Google Chrome. I'm sure the others are right when they say it is simply a Chromium bug.
-
They share a code base and are developed by many of the same people… and a bug that has been fixed in Opera after the split shows up in Vivaldi...
I'm using Windows 10 and it occurs 100% of the time the window is maximized. It happens as well on 7 and 8 but I did not do any focused testing so I can't say how often or under what circumstances it is replicable there. Just noticed that it was happening."They share a code base…" This is simply false. There is nothing in common between the code of old Opera and Vivaldi, and the only commonality between new Opera (which also has no code in common with the old Opera) and Vivaldi is Blink.
-
"developed by many of the same people…" There were, if I recall, about 100 developers at old Opera. Now there's about 60, it would seem. From people who were once, at some stage of its development, on the old Opera team, it looks as though between three and six of them are on Vivaldi's fifteen (or so) man development team. "Many" of the same people is a quite relative term - add to that the fact that it was never possible to use any of the old Presto-based code on a Blink base, and you have a commonality in personnel which would be, uhmmm, outside of philosophy, possibly, irrelevant.
-
On topic, I have on occasion noticed odd taskbar behavior on my Windows tablet while running Vivaldi; basically, whenever Vivaldi was maximized, it would "block" touch input on the taskbar; i.e. windows could not be switched and worst of all, it was impossible to activate the on-screen keyboard from the taskbar, and it would only resolve itself once I Restored the window from maximized. The past few days I haven't run into the problem, though, so it's very arbitrary.
-
They share a code base and are developed by many of the same people… and a bug that has been fixed in Opera after the split shows up in Vivaldi...
Humm, nope.
They do share a code base, Chromium. But the "split" you are saying never existed. Jon, the CEO of Vivaldi has left Opera before they went on the madness of dumping Presto and started a Chromium browser. Some of the Vivaldi team also moved away from Opera when they dumped Presto and I just guess few have worked on new Opera if they did. Those who worked on Opera before probably only worked on Presto Opera. And Vivaldi work has started many months before they announced it to the world.
-
For those not seeing the bug, are you running in a maximized window?
Ok I was finally able to reproduce the behavior you are talking about.
It affects Opium, Vivaldi, and Opera 11, but not Opera 12.
And, more important, happens just on win 10 (build 10041).
I tried Win 7, Win server 2008, win server 2012r2, win 8.1 and none of them is affected using any of the mentioned browsers.
Which is way different by the scenario you described.
So we are talking about a behavior shown on an unfinished operating system that has it's own oddities and it's own compatibility problems, and that will likely changed again and again until the final release (to say better until the first dozens of fixpacks after the final release).
No offense, but surely the glitches on win 10 should be discussed, but not like you did.
First of all you should made clear that you was talking about win 10, then blaming the developers for a supposedly unfixed bug for years was completely misleading and unfair.
-
@RRR13:
Stop insisting on the Windows 10 scenario!
It's a win 10 problem, to be more precise, is a win 10 Build 100xx problem.
A problem that is already solvable, just download "windows tiny borders",, set the border padding from -60 to 0, and reboot.
That's all.