Linked by Thom Holwerda on Wed 13th Feb 2013 13:21 UTC
Opera Software De kogel is door de kerk: as we already talked about earlier, Opera is going to switch to the WebKit engine, leaving its own Presto rendering engine behind. We didn't yet know if they would the switch only on mobile or on the desktop as well, and they cleared that up too: both mobile and desktop Opera Browsers will switch to the WebKit rendering engine.
Permalink for comment 552426
To read all comments associated with this story, please click here.
RE[4]: RIP Opera
by Kochise on Thu 14th Feb 2013 08:23 UTC in reply to "RE[3]: RIP Opera"
Member since:

1- On the JavaScript problem, here 12.14, try this :
"Qui, quoi ?" = "Centre equestre"
"Où ?" = "Pau"
"Recherche à proximité de" = checked

Once on the result page, scroll down and hover the map.

2- Yup, Opera always added new features, in the beta first, then in the "stable" release. But it always have a drawback, you have to get it all, almost no way to disable this or that feature one by one.

3- If they push new features, it would be cool they are fully functional and don't requires a dozens updates to get them fixed. The "visual mouse gesture" fiasco introduced in 11.5 was a pure mess no one ever understood why they pushed it without warning :

When I say I stopped reporting bugs, because it's always left open with no answer :

WebGL do not work :

Nothing changed, yet it's advertised as a major compatibility point. Nope !

Mails gets scrambled after Opera crash :

Never corrected, reseting the M2 client is still not possible without using tricks. And I don't speak about reimporting all the mails and mail accounts :

Soooo, since Opera is always focusing on new features without maintainting their old features, I give up.


Reply Parent Score: 2