There are two ideas :
# Allow to create in-line compatibility markers to provides quick information within our content.
# Provide a very quick visual hint on top of the page to tell which browser currently support the features describe on the page (it can be a logo or anything else).
# Allow The first idea is one of our functional priority as we already have such markers for Gecko/Firefox compatibility (but currently not bind to create in-line any formal compatibility markers data which requires some time consuming manual maintenance). The second idea is less important and require a deeper investigation as it can be tricky to provides quick provide an accurate information within . Currently on MDN, most of our contentpages contain information about several features at the same time or information about feature which evolved greatly over time. Therefor, such information can be often misleading if not handled very carefully. More specificaly, Such summary information can hide inter-compatibility problems: the "support" may mean "it can be made work in this browser", "follow the spec, but maybe with a couple of minor glitch", "follow perfectly the spec". The flexbox support is one example: most modern browsers follow the spec, but maybe with a couple of minor glitch. But flexbox was available in one way or another in browsers long time ago (but interoperability was a nightmare to achieve).
==== Compatibility Filters ====
