Vivaldi Browsercast: One Size Does Not Fit All! (Part 1)


  • Vivaldi Team

    We're starting off something new, and that's our Vivaldi Browsercast!

    This is the first of what will be many interviews with developers across the World Wide Web and how their experiences have helped to shape a user-centric model of browser development.

    See the full blog post here



  • First! And nice browsercast.


  • Vivaldi Translator

    Great browsercast! Looking forward to part 2 :)



  • I'm Vivaldi lover, not using anything else until Vivaldi's broken, but with that "HTML, CSS and JavaScript" we'll always be the slowest browser :(



  • But it is the only chance to give Chromium features. All other methods are way too complicated.

    Even Brave team has decided to not mess around with normal Chromium code as Chromium changes way too often and you would have a really hard time to implement features and being able to maintain them over a long period of time.

    It's either slower but feature rich or faster and having almost no special features.



  • "It's either slower but feature rich or faster and having almost no special features."

    That's not true at all though, all you have to do is have a look at Opera. They seem to be doing fine in the speed and feature department.

    I agree though that in the long run going with non-native GUI will be better. But that doesn't change the fact that I always get a little jealous of Opera's speed every time I decide to use it for few minutes.



  • Unfortunately the browsercast only in English. In german it would be nice also.



  • I could not agree more with everything Molly and Jon are talking about here and it is really heartening to hear that this focus, which was high on the agenda in the early days of Opera, remains now with Vivaldi.

    I believe maintaining a keen focus on accessibility innovation has net benefits for every user, regardless of their ability. Zoom, keyboard navigation, gestures, style overrides, just to name a few things that help us get the job done quickly and efficiently, with minimal stress.

    One thing I would like to see in Vivaldi is a way to hide floating divs, which can clutter up so much of the header and footer area of the viewport and reduce the visible area. On desktop this is a pain because the most comfortable position to read is at eye-level, near the top of the monitor. If there's a great big website menu banner at the top, I usually dive into the DOM and remove it manually using the debugger just so I can read more comfortably. On mobile, when that version arrives, this would return control of the valuable screen real-estate to the user!



  • New Opera does not have any recognizable UI customization features. You can not compare Opera new with Opera old or Vivaldi. Opera new does not feature power user features.

    It is one thing to add some buttons which gain access to a VPN or to include some integrated adblock or battery saving features, what Vivaldi does is completely changing the UI functions as a whole.

    This would be seriously hard to do in Chromium if you have to modify the normal Chromium source code. Also Chromium does not have that complex API to allow deeper UI customization features. Even normal extensions or apps are very much limited in what you can change.



  • Ah, I wish we could have them in every language. Alas, we go with English.



  • Thanks @wardies for the kind words as well as the interesting idea of hiding useless divs - this is the sort of thing that user style sheets were in fact created to do and as such, you can already make those changes yourself if you know how. We want to make it easier for you to do that without breaking things and give your user interface controls both at the level of the browser and the pages it's interpreting.



  • Thanks for the insight and kind words everyone! :) We have a long way to go and much to learn! I for one have learned the hard way that saying something will "always be" a certain way has not worked out that well for me!

    I suppose the point I want to make is we never know until we give it a go - and we're giving it a go. Is it a risk, a constant to-and-fro conversation about balancing performance and feature sets? Absolutely!

    And this is something I expect will continue as we take this journey and draw the map together along the way. HTML5, CSS and Web technologies are ever evolving and there may well be solutions to problems we don't even understand yet.

    Great risk can often bring great reward, I think. Do you agree :?:



  • You really should improve the privacy aspect. In that matter you can learn a couple of things from Brave browser - integrated adblock, noscript, fully being able to deactivate WebRTC, no fingerprinting.

    If you would be as privacy centered like Brave, Vivaldi would be the best. :)

    @MollyH but the most important thing, please reduce your dependence from Chromium. Vivaldi's UI is a feature split off from Chromium, so you use tons of bloat which is not necessary to have at all, as you do not even use it ;)


  • Moderator

    well … that's a good idea. any plans to include closed caption?



  • Molly: you make a powerful case for User Style Sheets. It's not just about accessibility, though, essential though that is, but about usability more widely. Although Vivaldi is my main browser, I still use Opera 12 when I need to. I have a range of User Style Sheets to customise pages according to my own usability preferences, e.g. exposing links clearly (now that the blue underscore convention is dead); suppressing navigation when printing; revealing potentially harmful iframes; showing page outlines (headings only); and many more

    Vivaldi's Page Actions are nearly there but need just a little more work to make them fully useful. I think Vivaldi could provide a better set of predefined User Style Sheets than the present ones.

    I posted a Feature Request in March and indicated the extra work that I think is needed.

    Thanks for the Browsercast.



  • I agree, and I think we've been driving the point of removing Chromium code node used or needed and replacing it with Vivaldi's code with web technologies for a while now. I wish we could have some sort of confirmation from Molly and the team, but maybe she's still researching on it.



  • @MollyH, since people are asking and your conversation with Jon was so awesome I've transcribed the entire podcast (and posted it to my Vivaldi blog). If the moderating powers that be approve it, at least people can then read/translate it.

    Feel free to reject/approve/move it to wherever you feel is more appropriate… it's your great content, after all! Looking forward to hearing future casts and learning more about this fascinating world and the people involved.



  • Thanks Molly & Jon. As have others before me, i found this interesting & informative. To improve the future casts, could you pls significantly reduce the "background" music volume played during your intro & afterword? For me that music was so loud compared to your voice that i had lots of trouble understanding what you were saying. It was a relief when the main cast content commenced, sans music, so i could understand all the chat. Ta.



  • Nice with a cast.

    A few issues:

    • Music in intro is too loud.
    • Get some better microphones and/or room to record, there is a lot of echo in this cast.
    • There are multiple audio cuts. (Could be the record/cast software which cuts the sound when there is silence)
    • I though the sneaky music in the end was another application on my machine. It does not really fit in, in the middle of a a conversation.

    I really had to concentrate to listen to it, because of the lowish quality.



  • Hi, will you be releasing this on pocketcasts? thanks


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.