A few of them work across many browsers actually. For example, if you enable the right tags you would get Regions in Chrome. Clip paths, canvas paths should work by default, while canvas blend modes should work on Canary and most of these should also work on WebKit Nightlies. Canvas Blend Modes should work in Firefox too.
I could have posted a screenshot but I thought it was nice to have people play with the demo within the browseer, probably will stick to screenshots next time.
This is very similar to issues in W3C specifications. I just think a bug tracker should be the primary reference material to track discussions around a specific bug. I wish there was a way to link to IRC channel discussion around this bug and otherwise if possible.
But nevertheless, I think it would be better if implementors summarize discussions outside of the bug tracker into the issue itself.
I have no issues with the process, but only concerned with the way this change was made. The issue keeps referring to https://code.google.com/p/chromium/issues/detail?id=55584 for "details", but there is nothing there except statements asserting how much of a "big problem" this is.
I think this is a bigger problem with large open source projects in general where implementors are oblivious to which functionalities developers cherish and value. Any change in such features would require a more thorough explanation.
It is most likely because Opera was almost the only lone browser that refused to have 'Mozilla' in its user agent string from the very beginning.
A lot of websites still use UA detection scripts from late 90s(!) which STILL do antiquated UA sniffing which means Opera does not get scripts, styles or markup because it does not seem to have the 'Mozilla' in its UA string leading to broken pages.
There is an easy fix if it is an irritant which is to select 'Edit Site Preferences > Network' from the context menu on a page.
Also, we would be much obliged if you could submit a bug report if you come across a site that does not render correctly in Opera: https://bugs.opera.com/wizard/
If you are a web developer, please do consider using feature-detection :)
That is a goal yes, but these are the defaults that work for us, and we hope they work for everyone else (and we do look for suggestions to improve these), but if it does not work for you, we actively advocate choosing the defaults that do.
The reasons for each of the choices we made is all within the comments of the source file, so it is easier to choose what to keep and what to change.
All of us involved in the project are pretty much "DIY" kind-of people :)
What we hope people do is to read through the source to see why we made the choices for defaults and pick and choose what they like and keep using them.
There are lots of defaults that were eye-opening to me that were suggested by the scores of contributors to the project.