Opera v12.17



  • Yes, Opera v12.17b1863 has the same search engine selection bug (as v12.15 and v12.16) but they have fixed how that bug works. Opera v12.17 does not hang on a start-up waiting for a response from Opera's servers. Previous versions were unusable until Opera's servers validate browser's configuration.



  • Meaning what? Are we going to get fixed version? And, who is making those versions? Anyway, I think that some1 should check new versions for privacy issues.



  • I have no idea what Opera ASA plans are.

    I have a long list of things I want fixed in Opera Presto. I doubt it will ever be accomplished.

    My observation on Opera v12.17b1863 is about it being usable compared to v12.15 and v12.16.
    Try working with those two when your router has no connectivity to the internet. You'll experience long UI hangs. (This however does not occur if your computer itself has no network connection, Opera checks if there are active network connections first)



  • 12.15+ were defective releases! Web site compatibility was badly broken. There are sites that works fine in 12.14, but fails in 12.15, 12.16 and 12.17.



  • @STNG:

    12.15+ were defective releases! Web site compatibility was badly broken. There are sites that works fine in 12.14, but fails in 12.15, 12.16 and 12.17.

    May I have some examples, please?



  • http://www.chapters.indigo.ca - cookies support broken in 12.15 / 12.16 / 12.17
    12.14 - ok.

    http://www.twitch.tv/directory/all - 12.16 and 12.17 (x64 builds, Windows) - can't show content.
    12.14 - ok.

    http://flashscore.com - Opera 12.16+ (x64 builds for Windows) - can't show content. Works fine in 12.14.

    h__p://www.prweb.com/releases/mgmbill/circumcision/prweb11482537.htm - crashing browser in 12.15, .16 and .17 (12.14 - ok.)

    outlook.com - broken in x64 builds (12.16 / 12.17).
    Works fairly well in 12.14 (no matter x86 or x64 build)



  • I confirm the upper four links, as the fifth - I have no account there.

    Most strange is the fourth one: that particular page crashes, I opened several others there - did not crash.

    Alas, this just proves people saying that Opera ASA goes downhill - while fixing one particular issue they break code somewhere else.
    :(

    (all my usual sites work well in v12.17)



  • @booBot:

    Alas, this just proves people saying that Opera ASA goes downhill - while fixing one particular issue they break code somewhere else.

    Wasn't 12.14 the last release before the Presto development team got laid off?

    It may even the case, due to this sloppy maintenance, that the new version has more severe security bugs than the old one.



  • Some people say that the last usable version is v11.64, since then - the decline became quite noticeable.



  • Yes, decline was noticeable, barely. But after 12.14, Opera movement toward Google became obvious. I consider O12.14 last usable version of Opera. And funny thing, there is x64 release of almost all version, but they are rather hard to find. Looks like Opera ASA deliberately wanted users to consider Presto Opera obsolete.



  • @booBot:

    I confirm the upper four links, as the fifth - I have no account there.

    Most strange is the fourth one: that particular page crashes, I opened several others there - did not crash.

    Alas, this just proves people saying that Opera ASA goes downhill - while fixing one particular issue they break code somewhere else.
    :(

    (all my usual sites work well in v12.17)

    Usually software that breaks in different diverse areas, like failing where it never failed before, comes from non-modular code. You can get so far with non-modular code but when the code starts to to work as Boobot describes, it is usually too late to repair.
    Just an observation.


  • Vivaldi Translator

    Hooray for the new release!
    It finally remembers my login for this site.

    I love the irony of this new version though.
    The only reason we got an update is because the updater was using OpenSSL.
    I had long assumed there would never be any more v12 updates, so disabled the updater thus actually avoiding any heartblead issue.
    :dry: So to fix the heartbleed issue, I had to enable the updater, temporarily exposing myself to the threat the fix is for :whistle:

    BTW. Originally Twitch worked fine in the previous version for me, until suddenly one day it did not.
    I just put it down to a plugin or my config, as this new PC has only ever had the 1 copy of Opera (til today).
    Oh and it still does not work in the new version.



  • @STNG:

    http://www.twitch.tv/directory/all - 12.16 and 12.17 (x64 builds, Windows) - can't show content.
    12.14 - ok.

    http://flashscore.com - Opera 12.16+ (x64 builds for Windows) - can't show content. Works fine in 12.14.

    outlook.com - broken in x64 builds (12.16 / 12.17).
    Works fairly well in 12.14 (no matter x86 or x64 build)

    Looking at the error console, it looks like they're all caused by the same bug. Something in the x64 version is causing some JS security to be tighter than it's supposed to.

    Twitch.tv issue is bug DSK-387153. Doesn't look that bug was ever seen by anyone.

    For the cookie issue, I'd just guess that it's due to the fix mentioned in http://www.opera.com/docs/changelogs/unified/1215/



  • People have seen the post in the Opera forums about the missing file in the 64-bit version, yes?

    https://forums.opera.com/discussion/comment/15175408#Comment_15175408

    The file should be in the defaults folder, but isn't.



  • @sgunhouse:

    People have seen the post in the Opera forums about the missing file in the 64-bit version, yes?

    https://forums.opera.com/discussion/comment/15175408#Comment_15175408

    The file should be in the defaults folder, but isn't.

    I wasn't aware. That seems to fix the twitch.tv, flashcore and outlook issues at least. (Didn't check the others)



  • @STNG:

    h__p://www.prweb.com/releases/mgmbill/circumcision/prweb11482537.htm - crashing browser in 12.15, .16 and .17 (12.14 - ok.)

    Just for giggles, I narrowed it down to:

    (nix newline format with an LF before the last font close tag)

    There's something similar to that in the framed page loaded with the last iframe tag.

    Opera 12.14 indeed handles that fine while 12.17 doesn't.



  • @burnout426:

    I narrowed it down to:

    Did you file that bug?



  • @booBot:

    @burnout426:

    I narrowed it down to:

    Did you file that bug?

    No, because it's for Opera 12. But, I'll inquire about these issues. Doubt it'll help though.



  • @STNG:

    http://www.chapters.indigo.ca - cookies support broken in 12.15 / 12.16 / 12.17
    12.14 - ok….

    Also for giggles, you can try this user js:

    window.opera.defineMagicFunction('checkCookie', function (oRealFunc, oThis, oParam1, oParam2)
    {
      return true
    });
    
    

    just to test if the site works fine then. The original function is failing for a good reason I assume though, so…



  • sgunhouse: Thanks for that link, I will copy that file from my Laptop (x86) to my Desktop System ASAP… as it seems I am to be considered lucky that I haven't encountered any real inconveniences so far with using 12.16 x64 - and now 12.17 x64 - Thanks 2 Opera, it was only via Google (oh well, well...) that I found the opera.com/* side where I could choose the Version to download and not only got directly linked to the x86 installer ( http://www.opera.com/download/guide/?ver=12.17 vs. just following opera.com(s) links) - I hope that is a real opera address as I just downloaded a few old versions for my archieves from the linked path (before it will be lost in time[&space] like tears in the rain)…


Log in to reply
 

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