MDN/Development/CompatibilityTables/Data Requirements: Difference between revisions

Jump to navigation Jump to search
Line 51: Line 51:
; Filter at the content level : The same as the above but directly into the content. This is something [https://support.mozilla.org/en-US/kb/how-to-use-for SUMO is doing]. However, the range of platform we want to cover on MDN is quite wider and such a mechanism on MDN could make things unnecessarily difficult to maintain.
; Filter at the content level : The same as the above but directly into the content. This is something [https://support.mozilla.org/en-US/kb/how-to-use-for SUMO is doing]. However, the range of platform we want to cover on MDN is quite wider and such a mechanism on MDN could make things unnecessarily difficult to maintain.
; Filter at the compatibility data level : In this scenario we want to let the user decide which compatibility data he wants to see. In this case, the content and the page remain untouched, only the displayed data are shown or hidden. The examples of filter upon compatibility tables (see above) is a good use case.
; Filter at the compatibility data level : In this scenario we want to let the user decide which compatibility data he wants to see. In this case, the content and the page remain untouched, only the displayed data are shown or hidden. The examples of filter upon compatibility tables (see above) is a good use case.
'''NOTE:''' ''This feature is good for browser data but is also a key point for Gecko internal APIs such as XPCOM components.''


==== Compatibility Search ====
==== Compatibility Search ====
Confirmed users
630

edits

Navigation menu