Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'Partial support' and 'Disabled by default' #199

Closed
saschanaz opened this issue May 19, 2013 · 4 comments
Closed

'Partial support' and 'Disabled by default' #199

saschanaz opened this issue May 19, 2013 · 4 comments

Comments

@saschanaz
Copy link
Contributor

Sometimes there are some notes like 'Partial support in Firefox refers to being disabled by default' as in SPDY item (http://caniuse.com/#feat=spdy). However, items including Web Audio, the 'disabled by default' browsers are treated as 'no support', as Firefox 21 partially supports it but with the option media.webaudio.enabled.

I think it's better to clarify this in the guidelines for contributing document.

I think additional

  • d - not enabled by (d)efault

is also good, because sometimes some browsers disable some features because they are yet in WD status, while perfectly support current specifications.

@saschanaz
Copy link
Contributor Author

But in that case, browsers that support a feature partially, not by default, and with prefix, would be marked as a d x? It sounds more complicated OoO

@foiseworth
Copy link
Contributor

Chrome is moving away from vendor prefixs and set to use flags to enable in-development CSS features. It would therefore be a good idea to further discuss this.

I would be in favour of items that require setting a flag having their own notation as @saschanaz suggests.

@Fyrd
Copy link
Owner

Fyrd commented Jul 27, 2014

Just added "d" as a possible value. For now it's added to a "n" and does not specify whether it's partial or not (doesn't seem as important since it won't be for all users anyway)

@Fyrd Fyrd closed this as completed Jul 27, 2014
@saschanaz
Copy link
Contributor Author

Good, I agree that it wont' be for all users, but at least users would be able to know that the implementation is ongoing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants