A first peek at Opera 15 for Computers comments

Page 3 of 3 (113 comments)

Left under the original article, as archived; 2 pages of comments could not be recovered.

• 

  artmilTuesday, June 4, 2013 3:57:00 PM

  http://www.rlamana.es/ventus/code/examples/desktop/
  Lol and all that moving to webkit crap was supposed to fix all the compatibility issues... The page works but a nice message is welcoming you that you should use a webkit browser...
• 

  QuHnoTuesday, June 4, 2013 8:36:39 PM

  Originally posted by artmil:

  The page works but a nice message is welcoming you that you should use a webkit browser...

  
  The message is technically correct - because Opera 15 is a "Blink" browser which is not identical to "Webkit" but a fork.
• 

  Rafael LuikTuesday, June 4, 2013 8:58:57 PM

  It wasn't supposed to fix ALL the compatibility issues, but the great majority was fixed.
  
  Browser sniffing or spec detection of a standard Opera hasn't already implemented in their browser (like being 1 version behind Chrome for some days) won't stop happening just because they changed the engine.
  
  BrowserJS is already present in Opera 15 for that matter.
• 

  XP1Wednesday, June 5, 2013 2:24:59 AM

  Originally posted by artmil:

  http://www.rlamana.es/ventus/code/examples/desktop/
  Lol and all that moving to webkit crap was supposed to fix all the compatibility issues... The page works but a nice message is welcoming you that you should use a webkit browser...

  It more of a browser sniffing problem than a rendering engine problem. The code checks for the vendor. Of course, Opera's vendor is neither "Google Inc" nor "Apple Computer", so the programmer incorrectly assumes that a WebKit-based browser can only be Chrome or Safari.

  var isChrome = /Chrome/.test(navigator.userAgent) && /Google Inc/.test(navigator.vendor);
  var isSafari = /Safari/.test(navigator.userAgent) && /Apple Computer/.test(navigator.vendor);

• 

  QuHnoWednesday, June 5, 2013 4:48:11 AM

  Originally posted by XP1:

  It more of a browser sniffing problem than a rendering engine problem.

  
  Same story as before with Opera 12. When I encountered problems on production sites, it was caused by stupid sniffing or using proprietary code in about 99% of all cases.
• 

  FransWednesday, June 5, 2013 10:26:06 AM

  Originally posted by QuHno:

  Same story as before with Opera 12. When I encountered problems on production sites, it was caused by stupid sniffing or using proprietary code in about 99% of all cases.

  
  +999999
• 

  artmilWednesday, June 5, 2013 3:16:49 PM

  Originally posted by XP1:

  It more of a browser sniffing problem than a rendering engine problem.

  
  Yes i'm aware of that.
  

  Originally posted by QuHno:

  because Opera 15 is a "Blink"

  
  Doesn't matter... different name the same engine for now - more time must pass before there will be some major differences.
  

  Originally posted by QuHno:

  Same story as before with Opera 12. When I encountered problems on production sites, it was caused by stupid sniffing or using proprietary code in about 99% of all cases.

  
  And that's why it's funny...
  Maybe i'm lucky but i don't remember when was the last time i encountered a broken page with presto... I'm also aware that part of it is thanks to browser.js
• 

  QuHnoWednesday, June 5, 2013 10:09:51 PM

  Originally posted by artmil:

  Maybe i'm lucky but i don't remember when was the last time i encountered a broken page with presto...

  
  I didn't say that it happened often to me - just what the problem was when it happened
• 

  Glen WhiteThursday, June 6, 2013 9:31:32 AM

  I think moving the email client out of the browser is a bad mistake on so many levels. I understand the thinking behind the move but I think it is a miscalculation.
  
  1) When I get annoyed with Opera (as I often do with all programmes) the thing that stops me changing browsers is the email client. Despite it's problems, it is still the best email client out there and it is a real shame it has not seen any love from you guys.
  
  2) Having an integrated mail/browser programme sets Opera apart from other browsers. Without it, Opera feels a lot like Chrome.
  
  3) If you have a separate email client it may attract new users on it's own. However, these users have no incentive to shift over to the browser.
  
  I would recommend, rather than a stand alone programme, more a downloadable extension/gadget/widget whatever thingy that users can choose to add to Opera if they wish.
• 

  toby5Thursday, June 6, 2013 9:35:11 AM

  Ok, new features looks great, but my excitement has faded away soon after I opened settings and noticed it is Chrome 2 indeed! Customization possibilities of Opera was one of it strongest points, but there is not much to set now.
  
  I don't really get it where my bookmarks will go, what about saved sessions? I want side panel back! Despite any Opera's flaws I gave up other browsers for these features.
  
  Maybe 15 it is more compatible but it's much more downgrading than upgrading. Thanks a lot! Hope you'll add much more to this, maybe wait until version 20, because 15 sucks!
• 

  Davit BabayanFriday, June 7, 2013 3:20:22 PM

  Originally posted by toscho:

  We want your Opera to feel native to your operating system — after all, it's probably the program you use the most apart from your OS.

  
  
  http://i.imgur.com/65tQnQ6.png]
  
  Win 7, simplified UI. Guess which program doesn’t respect the system UI?
  
  

  +1
• 

  Davit BabayanFriday, June 7, 2013 3:24:29 PM

  It will very usefull if Opera developers mix Stash and Notes.
  What you think about it ???
• 

  rbimSunday, June 9, 2013 7:22:14 PM

  Originally posted by theredgiant:

  This is a total disaster.
  
  Opera has just shot themselves in the foot.

  In the head. This is more likely. I'm happy Opera didn't release Linux version: now I have time to save/export tens of open tabs, notes, bookmarks, freeze version and prepare to migrate to other browser.

« Previous Pages: 123

« Back to the article