it always made me wonder why opera decided to spend time on svg

SVG is huge in the mobile/device space. You would be surprised.

No one argued that innerHTML or such things should be removed, by the way. Straw men will get you nowhere

and features? opera does not support setters/getters (yahoo used to use these, most probably use them up to this day). does not support oncontextmenu (due to inbuilt right click menu), does not support overflow-x, overflow-y css properties making pages look strange with vertical/horizontal scrollbars appearing randomly. list is longer, but i stopped following it as it ceased to be my job some time ago.

afaik these limitations are fixed in 9.5, but question is, are they fixed in a way other browsers use them, or in an opera-way. world is going nothing but ignore too-standard implementation, that doesnt match commonly used one.

and again, if you think browser should be as standard compliant as possible, remove innerHTML. it isnt a paper standard, it is ’standard’ because everyone use it. the secon case is THE standard. id prefer to have all browsers work the same, but due to lots of gray areas in w3c docs, this isnt possible. and stupidiest way of doing something is to implement something in a way different than all other browsers do it. opera did that many times before and now it is paying for it. i hope that they’ve learned their lesson.

Opera have all the features google need to code for it, although they don’t test in standards compliant browsers first do they? …

some of these ‘bugs’ are lack of features, not real bugs btw. features, that are present in IE/FF for years.. it always made me wonder why opera decided to spend time on svg that was a shadow to flash, and it was sure that it will never be adopted, instead of fixing their implementation of JS. and please, no standard rhetorics, if you are so standard lover, remove innerHTML implementation.

that question id like Jon to answer, abut in detail, not ‘we are working on it’

There’s one guy who fixed bugs in Google and he used a JavaScript thing for Opera which fixed Maps and Mail. Thing? Is this an actual quote from the CEO ?

if you look into the code xErath wrote you’ll see that, fuxed bugs are divided into opera bugs and google bugs. and i have to say, that there are lots of opera bugs. so even if google code would have been 100% correct it still would fail. google services failing in opera completly isnt as one sided game as opera would like it to be.

Anyway, I think this interview shows Opera’s core principles, and also why I love using it so much: The engineering behind the scenes is astounding, nothing already existing is sacrificed (too much) to innovate, and hastily made compromises are kept to a minimum.

And although my major at college is somewhat unrelated from software/web development (environmental engineering), I will certainly keep Opera’s design process in mind through my studies. But there is always that slight possibility I could change my major…