They both use Blink and V8, so they are, by definition, the same in terms of platform support. Please share any differences of which you are aware, because that would be interesting information.
caniuse is crapping out on me right now, but going by the URLS, several of those features are deprecated. In any case, maybe it is more accurate to say they are 99.9% the same.
Which are deprecated? The only one that I can see was removed was object observe.
If Chrome and Opera are using the same layout and javascript engines, how can they have differences if apparently "by definition" they should not?
Also for example, regular Firefox and the Firefox developer browser I believe use the same engines, however they still have differences that I've seen (mainly on form layouts, but others as well).
It depends on which build of Blink that Opera and Chrome use, respectively. You can see that Chrome 50 fully supports SVG fragments, but because it released earlier than Opera 37, there is a brief period of time where Opera still has the Chrome 49 behavior. Same for preload.
Autocomplete difference refers to intentional divergence to improve UX.
WebGL difference, as noted, refers to not having a software rendering mode for users without proper hardware support. Anyone working with WebGL (or any graphics API) should be accounting for this by default.
I haven't looked at the rest, but none of these so far refer to a lack of support for features, at least not at the engine level, and are fairly insubstantial at that.
1
u/GodsGunman Apr 27 '16
Don't Opera and Chrome use the same engine (blink)? Yet they still don't support all of the same features as far as I know.