//Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/35 //

== Narrative ==

As a user, I want to know if a beta feature doesn't work work for my browser or technical configuration.



== Acceptance Criteria ==

Browser and technology compatibility can vary from one feature to another (VisualEditor in particular isn't available for IE yet). Other features may require Javascript, CSS or other technical configurations as well, that could cause them to malfunction if not enabled.

So each beta feature extension needs to have a blacklist of platforms that it cannot support, stored in Javascript, JSON or other machine-readable format that can be sent to Beta Features.

The Beta Features (or the extension) then needs to check whether the user's configuration matches one of these restricted platforms, so it can let the user know if their platform is not compatible with that feature.

Last but not least, we also need to inform the user about features that are not compatible with their particular browser or configuration. For example, we may want to display a message like: "This feature is not compatible with your browser yet."

This is required so the user understands why they cannot enable that feature (even though it's still checked in their preferences -- so they can use it on other platforms).

That message could be bolded and/or colored in red, to provide a visual cue that this feature will not work. Maybe the entire feature could be grayed out, to make it even more explicit?

Here are the types of notes we may need to display, when a feature is not compatible for the user's configuration:
* Notes about browser compatibility
** Text displayed to user "This feature is not compatible with your browser yet."
* Notes about JS compatibility
** Text displayed to user "You must  [[http://www.enable-javascript.com/ | enable JavaScript]] in your browser to use this feature."
* Notes about CSS compatibility
** Text displayed to user "Your site skin or custom CSS is not compatible with this feature, to enable it use the default site skin."

Only one error message should be displayed at any given time, the order of display should be as follows
# CSS/Skin compatibility
# JS compatibility
# Browser compatibility
e.g. if there is both a browser and JS compatibility issues the user would only see the JS issue.

See the most current feature requirements here:

 [[https://www.mediawiki.org/wiki/Beta_Features#Tasks | https://www.mediawiki.org/wiki/Beta_Features#Tasks]] 



== Related Bugs ==

== Related Stories ==

 [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/2 | #2]]  Beta features

See also:

 [[https://www.mediawiki.org/wiki/Beta_Features#Tasks | https://www.mediawiki.org/wiki/Beta_Features#Tasks]]