Vivaldi Version Number should equal Chromium's "Version Number" AND DROP THE UNUSED ZERO!



  • Vivaldi Version Number should equal Chromium's "Version Number" AND DROP THE UNUSED ZERO! This is a usability issue with "Browserscope" and like websites and applications. -- [url=http://www.browserscope.org/ua]Browserscope's User Agent[/url] FOR THIS UA STRING ... "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.99 Safari/537.36 Vivaldi/1.0.291.18" THE VERSION SHOULD BE ... " [rest of UA string for compatibility] Vivaldi/45.2454.18" Note : THE ECMA "Javascript Agent" and "Browser Agent" in Vivaldi seem to be identical. Yes, this browser is very buggy but the User Agent and Version issue should be in sync with the deployed code.



  • Hi, really a nice first post. :/
    These are release numbers and Vivaldi is not released, it is alpha software.
    It is buggy, slow and not feature complete.
    We alpha testers want to help the Vivaldi developer to get the bugs sorted out and make it as fast as possible.

    Cheers, mib



  • Do you have written to google that they should drop the unused zero ;-)

    Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36



  • @aspadistra:

    "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.99 Safari/537.36 Vivaldi/1.0.291.18"

    THE VERSION SHOULD BE …

    " [rest of UA string for compatibility] Vivaldi/45.2454.18"

    Why? Does the actual formal cause any problems with websites that parse the UA string? Otherwise i disagree.


  • Moderator

    I dont really see any real argument that Vivaldi has to have the same versioon number like Chrome.
    Where is the problem?
    The Chromium and Vivaldi version can be parsed vom UA string.

    Webapps should not rely on version strings at all to check for browser abilities. :evil:

    @aspadistra
    AND YOU SHOULD DROP YOUR LOUD SHOUTING HERE! :whistle:
    BAD BEHAVIOUR!



    1. Chrome is at version 45, but Vivaldi isn't. Vivaldi doesn't even have a beta yet
    2. Tell google to remove the '0' from their own version number
    3. If we only keep what should be in there, it would only say "Vivaldi".
      I seriously do suggest that someone starts a "workgroup" to standardize those user agents.

    Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.99 Safari/537.36 Vivaldi/1.0.291.18

    In short that user agent basicly means as much as: Vivaldi pretending to be chrome pretending to be safari using 'applewebkit' and pretending to be 'KHTML' pretending to be Gecko pretending to be 'Netscape'…
    (For an interesting read see: http://webaim.org/blog/user-agent-string-history/

    Version issue should be in sync with the deployed code

    So, (seeing point 3) It already is. It's vivaldi 1 pretending to be chrome 45



  • Calm down.




Log in to reply
 

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