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.
Thread beginning with comment 552392
To view parent comment, click here.
To read all comments associated with this story, please click here.
cdude
Member since:
2008-09-21

If there is demand for a certain feature they can and will add it. They have now even more forces to do so since lesser work on the rendering-engine is needed. If there is no demand then indeed, that feature may gone.

If you had a look at WebKit code and development you wouldn't argue about 10 inches deep layers nobody can touch. That's not reality. This isn't IE :-)

Edited 2013-02-13 21:52 UTC

Reply Parent Score: 2

telns Member since:
2009-06-18

Umm... I have. I have done some custom [proof-of-concept] type projects using the Qt5WebKit codebase.

I like it just fine. But that doesn't mean that it will provide 100% of what Presto provides in a convenient way.

I would say exactly the same thing in reverse if someone were trying to take the Presto engine--which I am sure is also a good code base--and stick it into a long-term WebKit project.

Edited 2013-02-13 22:59 UTC

Reply Parent Score: 3

cdude Member since:
2008-09-21

Qt5 QWebKit doesn't expose all the functionality and flexibility WebKit offers.

Opera also already started on that. They just pushed patches to improve HTML columns in WebKit. So, this extending where they see need isn't theory but it already is happening successfully.

Reply Parent Score: 2