Snapshot 1.5.604.4 - Fix for HTML5 audio and video on Windows
-
They are planned. They are not easy to do. What you refer to as "cosmetics," many users refer to as "important features." Plus, again, design decisions do not affect development priorities or pace. And the fact that the vast majority of users are not on touchscreen devices, means that touchscreen at the moment does not take priority over detaching tabs by dragging, improved history, email, sync, fully functional bookmarks bar subfolder menus and options, etc. MORE users, by far, have complained that they can't dock developer tools to the bottom of the window, than have said Vivaldi isn't fully compatible with their touch screen. Development priorities will always be at least somewhat weighted by the numbers of unique users who give favorable and unfavorable feedback. It could have happened, for unfathomable reasons, that Vivaldi users turned out to comprise a much larger percentage of touch-screen users than seen in overall market penetration. But it didn't.
Now every NFL coach, assistant coach, and coordinator uses a Microsoft Surface device on the sidelines. In that industry, there is deep penetration of touch screen for work use. Of the literally hundreds of persons I know who use a computer to DO things, to accomplish work, only two (my daughter and son-in-law) do work on a touch-screen device (IPads, for which Vivaldi is not available). The others don't own a touch-screen device or don't use it for work. I can't speak to recreational uses of touch-screen devices, even "all-in-one" HP desktops which accommodate all inputs, but I do know that their market penetration as to "pc-style" formats, for which Vivaldi is currently written, is extremely narrow and shallow.
So what you are asking is for Vivaldi developers to divert their attentions from expanding the usefulness of the browser on MOST target devices to expanding its compatibility with a narrow slice of the market.
Now I don't run Vivaldi, or even develop for it. But if I did (and I do run my own businesses), I'd reject your suggestion as to where I should concentrate my attention with limited resources, because as a business decision-maker, I know better. That said, Vivaldi has no limits on where they want to expand their market. They would want all modern personal computers covered in time, irrespective of input models.
-
Ayespy, he's just being deliberately provocative and making us waste our time. He understood what you and all of the others have said perfectly. Now he's throwing temper tantrums like a 2-year-old because Vivaldi is not adjusting their strategies or redirecting their development efforts to cater to his immediate needs.
-
Ayespy, he's just being deliberately provocative and making us waste our time. He understood what you and all of the others have said perfectly. Now he's throwing temper tantrums like a 2-year-old because Vivaldi is not adjusting their strategies or redirecting their development efforts to cater to his immediate needs.
Are you sure?!
I am not asking you or Ayespy, for none of you can reply to any requests, which can only be done by the developers. What I write here is only directed to the developers. And, I am sure they read our posts. This is their blog.I like Vivaldi not for the colours, not even for the speed dial, but for its tab stacking. If the developers can add touch screen abilities to Vivaldi, and allow us to use it in tablets and touchscreen laptops, I'd be happy. If anyone else think, they don't need such abilities in Vivaldi, that's their problem. What I can't understand is why some of you fight with me for having a request! And, the request is directed to the developers.
-
Christoph142 replied to you directly and said:
Yes, touch screen gestures are on our (long) list of possible features, but there's no concrete timeline yet.
What part of his answer did you not understand? You may not agree with his response or Vivaldi's priorities but that's your problem, not their's. I doubt that they have anything further to say on the matter. Deal with it.
Also, the folks here were not fighting with you, just patiently trying to explain why things are the way that they are.
-
Ayespy, he's just being deliberately provocative and making us waste our time. He understood what you and all of the others have said perfectly. Now he's throwing temper tantrums like a 2-year-old because Vivaldi is not adjusting their strategies or redirecting their development efforts to cater to his immediate needs.
I'm wasting some time on a Sunday, anyway. I can waste it watching some racing or some football, or waste it nattering with chdsl. No cost to me either way.
But while I'm thinking of it, browserA for PC and browserA for mobile are often completely different products. And a tablet is not a tablet is not a tablet. ONLY Microsoft, to my knowledge, tries to use the same (or substantially compatible, with the same name) OS on both PC and mobile, eg, Win8 and Win10. So making something "tablet friendly" (which Vivaldi fully intends to do in time) is really, at minimum, at least two different tasks. 1) make it run on Atom, Exynos, NVidia Tegra, Snapdragon, Media Tek, etc. and format it for a compact touch interface and 2) make it optimally responsive to touch interfaces on PC devices, some of which may have detachable keyboards. They really are two very different jobs. There is a third hurdle, if one wants to penetrate the Apple mobile market (iOS), and that is to design it to run on Apple's preferred WebKit engine and jump through all the other hoops to convince Apple to permit it to be included in the online app store, so that it can be installed on iOS. Very, very few browsers have ever cleared that hurdle.
-
Go for it, and enjoy the rest of your weekend!
-
Now that you have put some thought into this, have a look at the competition, Opera.
-
The competition, Opera, is an advertising company (where the revenue comes from to pay a development staff) that also builds browsers. They build three totally different products for PC and Mobile, and the first one for mobile (classic/mini) was written years ago on Presto, and is still published on that engine. The newer mobile product, crafted by their 100+ development staff, was introduced after the switch to the chromium engine. It runs on mobile because it is built exclusively for mobile. That said, it took them many months to release it for phone, and many more to release it for Atom-based (and similar) tablets. The Presto one is still the only fast one. Their PC product, developed using native elements on the Chromium engine, also with a relatively huge development staff, has touch-input code built in, due their use of native elements. Also because of the native element architecture, a relatively huge development staff still makes slower progress on the final product than does the tiny Vivaldi staff, AND they are blocked from implementing features which we enjoy (took them nearly two years to figure out how to incorporate a side panel, which can exist in only a single position, and they still don't have tab stacking or tiling, vertical tabs, movable toolbars, themes, editable gestures, hierarchical speed dial folders, icon-only bookmark bar (if you want it), ability to hide or reveal each part of the UI, horizontal menu if you want it, true tab pinning, quick-commands, etc.) But most importantly, such features as these I just mentioned are actually the raison d'être of Vivaldi. The price of being able to fulfill their primary mission, for Vivaldi, is not being able to implement some native features as quickly as Chrome imitators can.
The "issues" you are experiencing here with people EXPLAINING things (not "fighting" you) stem largely from the fact that you don't seem to grasp Vivaldi's prime mission. It's not trying to win the browser wars or supplant any of the big name browsers. It is all about features and options and flexibility, which were lost when Opera jumped to WebKit.
I used Opera exclusively and participated actively in discussions with their developers from 1999 until Vivaldi stole me away, Jan 27, 2015, and I still track their Beta, for the sake of being informed. I kinda know what they are about.
-
Well - that was interesting. Had a long and informative comment here, edited it, and it vanished. Looooooong story short, comparing Opera and Vivaldi is comparing apples and oranges. They are built from different technologies, to fulfill different purposes. Plus, as a sixteen-year member of the Opera community (who continues to track their Beta stream), I probably know more about it than I do Vivaldi.
Opera can't do what Vivaldi can do, which is why I switched to Vivaldi Jan 27, 2015.
-
Vivaldi's prime mission is to create an universal web browser, which user would want to use. Maybe most users want a browser to browse the web, most times in an idle way, but some users need a browser to work with. There was a time, a browser was just a tool to browse the web, but not it is what I use to work. Long years of using the mouse, brought in certain wrist problems, which a touch screen had helped to get rid of. Laptop is my work desk. Those days, I didn't need a browser so much, but now I need a browser for daily work. I am not a fan of any browser, or any operating system, for they are only tools. Tab stacking eases my work, so when I need to use Linux, I'd use Vivaldi. But, in Windows, I won't use it, as it'd a foolish not to use the touch abilities of that OS. In RemixOS, Chrome has the tab stacking ability and its very easy to move back and forth with a finger.
-
Periodically I download the newest Opera Developer and honestly wonder why they even bother with the project anymore? The UI alone is messy and illogical; confusing and looks unfinished. Vivaldi, on the other hand, presents a UI that fits so naturally into my workflow. It is an unmatched fusion of science and art.
-
Your comment reached my e-mail.
-
I'm new here (but not to the Vivaldi browser). I had a look in the forums but got overwhelmed – so forgive me for posting this here. On the 1.5.604.4, which I run on W8 -
- you broke my search engines! When clicking on a link in the list of search results, I just get a blank tab. I have to copy the link manually and paste it in a new tab. Wasn't a problem in Vivaldi 1v3-582.3 x86.
- the "close tab" (X) is never visible on the active tab, until I mouse-over on any other tab stub, then it appears. There's always CTL-W, but it's still annoying. Something so basic...
Look forward to fixes for these, otherwise a terriffic browser. Good work!
-
Can I add some items for the wishlist? One of my main considerations when switching to Vivaldi was that the bookmark handling is better than the rest, but it can be improved: -
- when I search for a bookmark and find it, I want a way of knowing where it is.
- when I hover over a bookmark, I want to see a bubble with the description and nickname.
-
Development of bookmarks is likely just resting now. While usable, I believe A LOT of work needs to be do on it. My suspicion is since it functions in basic form resources are being allocated to other parts of the browser. Your 1 is much needed, and I'd like 2 as an option.
-
It was a great comment. One of your points that I liked in particular was that it's important to understand Vivaldi's raison d'être - they are not trying to win the browser wars but rather to bring back some of the great features from Opera classic that were lost when Opera transitioned to a Chromium base. Vivaldi's approach also has allowed them to implement a formidable feature set very rapidly, and outpace Opera's own development efforts despite their head start. Vivaldi also accepts the fact that their product will not appeal to (or meet the needs of) everyone out there, and they're perfectly fine with that.
-
The percentage of web browser users whose needs won't be met by Vivaldi will likely be VERY small.
-
They bother with it because they have over fifty million users on desktop, and generate ad revenue from that. It's far from their main source of revenue, but it's part of the company model.
-
50 mil users for Vivaldi would be good too, but it can't be achieved with cosmetic changes. A company needs profits to stay alive. So, let the touch screen abilities come. Why are you guys against?
-
If you open the Nvidia Control Panel, select Manage 3D settings and under Program Settings add Vivaldi and enable VSync, does that fix it for you?