Snapshot 1.4.589.2 - Vivaldi 1.4RC 1
-
Please make the removal of the custom themes easier: add a cross icon or a context menu. Now it jumps back and forth switching themes when you delete your custom themes one by one.
-
Not sure whether or not this was intentional, but it looks like WebUSB is now enabled by default in Vivaldi. However, I can't find any way to manage USB devices like you can in Chrome.
And a minor UI issue…
On OS X, if you enable "Use Native Window", the Tab Bar does not reduce in height, and the stacked gradients of the Tab Bar and Title Bar look rather unMac-like. (If this was a deliberate design improvement for the other platforms, would it be possible, in future, to add an option for Safari-like tabs under the URL bar for us Mac users?)Thanks!
-
A new version of Chrome just came out with 33 major security fixes. I'm sure that users on the Stable channel would appreciate getting these fixes ASAP.
-
- Some ressources can't be reallocated. It's like making a baby. If you take 9 women, does it takes only 1 month ?
- What you consider "shit" is the gold of other users. Read above your post : "Middle click on trash to reopen tab makes me feel all warm and fuzzy inside." We don't all have your clearly impeccable tastes (nor politeness).
- Vivaldi is its name. Not ViValdi. So, call it V if you must.
- Providing a timetable isn't possible, because nobody knows what will be the browser in 6 months, not even the devs. They can tell you what they are working on right now, and what will probably come in the next few weeks but that's all. It's like asking "What will you eat for dinner February 17th ?". You can't answer that. You can answer it for today, maybe for tomorrow and the day after, but that's all.
- What does Firefox have that Vivaldi doesn't ? Be specific please.
- I don't believe Vivaldi ever tried to sell itself to the "prosumers", whatever that word means.
- Vivaldi is free. Why are you complaining ?
8 ) And finally, also, what are the functionalities that you are waiting for ? Please be specific too.
-
Can you provide a page where WebUSB works in Chrom(e|ium) and not in Vivaldi ?
As for the UI issue on OS X, I can't test, as I'm not on OS X, but on Linux, activating the "Native Window" means only to use native decoration, meaning the title bar, the trouple buttons (close, maximize, minimize), and the border all around the window. Nothing else. I don't believe that there is any other modification of the UI, but I could be wrong.
Thanks for your help !
-
I agree, but Henrik who did the themes, and the themes scheduler, isn't a dev exactly (even if he is learning), but he was hired as a designer. So, doing this feature didn't took ressources away from anything else, it was just what was available to him.
You can see his answers to the same question above, but if you sum up, he did exactly his job, as it's a "design feature"
-
Can you try to do Command+ { or } (without the shift) and/or to reassign them ? There was some work done in the way shortcuts are captured, and some changes are (more or less) expected.
Having those details would be very useful
(if you can also provide the keyboard layout you are using, it would be perfect ! ) -
I have a problem in the themes panes in settings; the design is now messed up a bit. The themes now have only four columns, when before they would fill up the entire row before starting a new column. Looks uglier this way.
-
Yep, it has been discussed will come probably later in a "v2" of the feature
-
I open my settings in a tab, btw.
-
I don't actually use WebUSB. However, El Capitan introduced a major update to the Mac's USB stack while providing compatibility shims for applications that use legacy API's. It's not perfect. With the recently added WebUSB support, Chrome periodically enumerates USB devices on the system, and this can trigger a crash in applications that use the legacy APIs for user mode device drivers if they don't do their exception handling quite right. Vivaldi now does the same.
The only point that I'm trying to make is that Vivaldi now appears to have Chrome's WebUSB code enabled, but does not provide a UI to manage those devices like Chrome does.
As for the Native Window option, on OS X, this causes the window (with Title Bar) to be drawn with native widgets. In previous releases, there was no gap between the top of the tabs and the "Native Window" title bar when you enabled the option; now there is. It makes things look better if you have extreme rounding on your tabs, but also consumes more vertical space.
In previous releases, the tab bar had no gradient, now it does… which looks great (because it matches how native apps like Safari appear) without the Native Window option enabled, and ironically very non-native (and annoying so with some colour combinations) when the Native Window option is enabled.
This is not a complaint because I think that Vivaldi now looks and feels better on the Mac than it ever has.
-
Two issues with this update (and previous too):
-
page scrollbar on the right is always gray on gray, no matter which theme. It's often practically invisible.
-
full screen youtube videos sticks to the bottom, but should be centered. There is progress, though - previously they were stuck to bottom AND to the right which made vertically recorded videos hard to watch.
Great work anyway, guys, thanks!
-
-
Just use the link on bottom of this blog post before comments to download the snapshot. Drag/drop into application folder and let it replace. Your profile (settings/themes/bookmarks/etc.) will stay intact – no harm in updating manually.
-
I actually thought of the middle-click-to-restore-tab feature myself yesterday. Great minds think alike, I suppose.
Also, the theme scheduling feature is one I would never have expected, but it's a great idea, and I appreciate it a lot! Now, if it could change the Speed Dial as well, it would be perfect.
-
They increment the version number when they jump versions on Chromium, pretty much. If the move from Chromium 52 to 53 doesn't break a lot of things, if security updates warrant it, and if there are any new features to roll out, there's no reason not to step from Vivaldi 1.3 to 1.4. Normally more testing and refining at the new version number would occur in the snapshots before a Stable, but also, normally, there would have been NO more 1.3 releases after the 1.3 Stable - but there have been some snapshots and a Stable minor update. So a lot of the work that might otherwise have been being done on 1.4 snapshots occurred under 1.3 instead. Plus, security updates argue for an earlier release of this version than otherwise. All that said, it seems a bit pointless to worry over what numbers are being used on new versions.
-
Can't be sure, but I think this bug is fixed internally. Keep an eye for next version, to see if it makes it in.
-
You don't understand the difference between developers and designers, do you? Vivaldi has developers. They develop. Vivaldi has designers. They design. Would you have Vivaldi fire the designers and hire developers in their place? Would you have the designers, who are not trained as developers, do someone else's (developers') jobs instead of their own? Color palettes are design. Shapes, sizes and colors of internal icons and buttons are design. Themes are design. Theme scheduling is design. It was written by someone who has no developer credentials. It was his (their) job. Vivaldi has other non-developers on the payroll as well. They do things like ambassadorship to the development community and work on standards and accessibility; sales and advertising; managing the Vivaldi Community websites, etc. Is it your position they should stop what they are doing and crowd in with the developers and start writing code? Design =/= Development. When you see design changes, don't let it worry you that someone's not on the job.
-
Keyboard layout is US.
Cmd { or } work as expected - they are assigned to Back and Forward.I removed Shift Cmd { and } and then reassigned the shortcuts to exactly what they were before and now it works.
-
Gray icon is not in the UI yet. As to the numeric keypad thing, I THINK this is being worked on.
-
Can you tell me what you have changed with the side panel because I used css to make it a dropdown menu instead with the buttons nested on my addressbar. Since 1.3 the buttons no longer show but developer mode says they are still there.
Also, the new theme layout wastes space using only (horizontal) lines of 4.
