Custom Speed Dial thumbnails – Vivaldi Browser snapshot 1.10.862.6
-
@duarte.framos I don't disagree at all, and actually made the exact same points that you just did in a previous post. The reason we have the awesome browser that we have today is because Vivaldi took a platform-neutral approach.
That said, on macOS, there are a lot of things that look and feel out of place on the platform because Vivaldi tries but doesn't really conform to platform norms. It also lacks some of the basic platform integration that macOS users expect. Other "non-native" browsers do a better job of it and this is something that Vivaldi should aspire to do better as well. These "little" things matter, and that's the point that other users were simply trying to make.
To some, having a truly native look and feel is also just as important as it is for others to be able to apply a wooden veneer to the entire browser chrome, or to have Vivaldi "work like it does on Windows" on all platforms.
-
@xyzzy Currently there are only two minor problems on osx I feel. The absence of switching to the desktop Vivaldi is on, when you open a link from another one. The greyed out/disabled minimize button after being in fullscreen. Other issues I apparently don't care about, I wouldn't call it a problem overall. If you want a browser that is made for the osx environment, your best bet is Safari.
-
@luetage I'm not bashing Vivaldi. Quite the opposite. I want Vivaldi to grow and gain marketshare. However, as an advocate for the Mac community and the Vivaldi community as a whole, I'm simply agreeing with valid points that others are trying to make, including yours.
You have your issues that you would like to see fixed. My primary wish list consists of a Bookmarks menu, for colours and gradients to be faithful to the native OS, and to be able to set Corner Rounding in themes so that buttons and the URL bar can look right without other elements (that should be square) looking like squircles. Some want better macOS platform integration -- e.g. Services integration, Keychain integration, to be able to input emojis with Control-Command-Space, for Data Detectors to work properly... Others want Vivaldi to work with their third-party window manager, or for windows to simply maintain their correct size when you open a new one.
Some of the "native widget" advocates here could be Windows users too, but I understand and empathize as a Mac user as well.
The key to making any product better is to focus on your strengths and to improve on your weaknesses. If you don't, you'll die a death from 1000 paper cuts.
-
@Ayespy
I see all the reason against a native interface, but it does not have to be all native. Most of the features are connected to the engine and the internal pages. That's where the JS approach is very good. But a native window frame, including the scrollbars and native menus are not something they change every day. The only other component are the toolbars, but the appearance of those can be mimicked quite well even with CSS. I don't think it's such a huge task. -
@xyzzy
It has the same problems on Win7 too. -
@Nekomajin A developer could explain it better, but Vivaldi-level configurability with native elements is, exactly, "such a huge task."
-
@pettern Love it and am thankful how responsive you were on this. Can't find another software creator like Vivaldi.
-
@xyzzy said in Custom Speed Dial thumbnails – Vivaldi Browser snapshot 1.10.862.6:
To some, having a truly native look and feel is also just as important as it is for others to be able to apply a wooden veneer to the entire browser chrome, or to have Vivaldi "work like it does on Windows" on all platforms.
Only a side note:
It does not look and feel 100% native on Windows too. That's one of the disadvantages of the approach they took and some people might not like it or miss something that a native approach would have.
The big advantage is, that it works like web pages: More or less everywhere the same (maybe apart from bugs that are only triggered on one platform but not the other - but those are bugs and as such a completely different matter). -
@Ayespy
What can you configure on menus and scrollbars? -
I do not understand the following:
Remove Winsparkle from Vivaldi and always use the UpdateNotifier for updating (VB-26833)
But when I updated today it looks like you still use Winsparkle. So does this mean that you do not use Winsparkle for the update notifications anymore but in general still use it?
-
@Gwen-Dragon
OK, no temp folder, but how would you be able to have the autoupdater run unless you had vivaldi processes also running? Doesn't make senseHowever, just got autonotified of an update, and it's worked as normal - tho' not a delta, but a full dl.
Whatever the problem was, its "gone away" without my making further changes.
thanks for your attention anyway
-
@wojcieche: thank you
-
@geertlp168 Yeah, the Devs all got together & decided to do all that just to specifically piss YOU off. Success! The plan is, one day after you've slammed the door shut, all the goodies arrive. Bye!
PS - All the rest of us clearly are merely loony masochists by using V, given the massive disaster you've portrayed. Unless, of course, you're wrong...
-
@geertlp168 The last time you posted anywhere here was back during the Vivaldi 1.2 release cycle. No specific problem reports, no requests for any assistance. Based on your words, you'd think that Vivaldi would be totally unusable but that's clearly not the case.
If you're experiencing a problem with Vivaldi on Linux Mint, please kindly post in the Linux forum. Others will either confirm your issue (and assist you in filing a bug report) or help you to resolve it.
Vivaldi is not like other corporations that release features, ready or not, based on a schedule.
Lastly, if you still feel that strongly and would like to close your account, you'll find the directions on how to do that here:
https://help.vivaldi.com/article/delete-account-on-vivaldi-net/Thanks.
-
I've just visited http://html5test.com site which claimed me I am using "Vivaldi 1.91".
So I looked to Vivaldi About page and in the User Agent there is really:Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.90 Safari/537.36 Vivaldi/1.91.867.3
Interesting... Is it a bug or intention?
-
@nfsmaniac see the reply to the same question previously on this thread
https://forum.vivaldi.net/topic/17235/custom-speed-dial-thumbnails-vivaldi-browser-snapshot-1-10-862-6/126 -
@iAN-CooG Thanks, but I'm confused from @Gwen-Dragon's answer:
Some websites do not detect Vivaldi correctly and they do not know about newer 1.10, they check only for 1.9 numbers, thats wh the UA has such big version number.
The problem is not in detection. The problem is already present in the User Agent string by which is Vivaldi identifying to web sites. In other words: Vivaldi itself is claiming itself it's a Vivaldi 1.91. Vivaldi has bad "identification card" so also sites are not able to read it correctly.
-
@nfsmaniac you got it wrong, I don't know which sites exactly, but they confused 1.10 with 1.1, while with 1.9x they think it's 1.9... the solution should be fire those idiots hired as webmasters and let someone knowing what they're doing fix the websites.
-
@iAN-CooG So you want to tell me that in the Vivaldi Team there are idiots to be fired too?
Oh, it's so bad...This is the "identification card". This complete UA string is processed by webmaster's code. Webmasters may be bad programmers so they make bad program to process this full UA string. But when already the input is bad, bad is also the output (=result of the UA processing program).
-
@nfsmaniac you continue to not understand what happened. In the first 1.10 snapshots UA was 1.10.something, as it should. Some websites, no specific name was made to me, so I don't know which, by reading 1.10 in the UA, they misinterpreted it as 1.1, and probably gave error saying the 1.1 is outdated. Vivaldi team must have temporarly worked around it by replacing the UA in the subsequent snapshots as 1.91, tricking those sites in believing it's Vivaldi 1.9 (not 1.91, they don't even read the 2nd cipher in the minor release).
For sure this issue with those sites should be resolved before the actual 1.10 release, it would be a pity that due to some minus habens not able to read properly a UA, Vivaldi should stick to a madeup UA forever...