Skip to content

Conversation

@bennypowers
Copy link
Contributor

No description provided.

@bennypowers bennypowers force-pushed the animation-effect-timing branch from 74fab7f to bc58235 Compare February 11, 2018 08:17
@teoli2003 teoli2003 added the data:api Compat data for Web APIs. https://developer.mozilla.org/docs/Web/API label Feb 11, 2018
Copy link
Contributor

@teoli2003 teoli2003 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, Benny!

This is really good, you didn't hear about the "flags" directive, so I linked to its docs where you need to use it. But besides of this, it is overall really good! Almost ready to land.

},
"firefox": {
"version_added": "48",
"notes": "The Web Animations API is only enabled by default in Firefox Developer Edition and Nightly builds. You can enable it in beta and release builds by setting the preference <code>dom.animations-api.core.enabled</code> to <code>true</code>, and can disable it in any Firefox version by setting this preference to <code>false</code>."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We use the "flags" directive to indicate that support (in release) is behind a flag. See the docs for more info and an example of use.
In this case, we also have to reformulate the note to say that the preference is on by default in Firefox Developer Edition and Nightly builds.

},
"firefox_android": {
"version_added": "48",
"notes": "The Web Animations API is only enabled by default in Firefox Developer Edition and Nightly builds. You can enable it in beta and release builds by setting the preference <code>dom.animations-api.core.enabled</code> to <code>true</code>, and can disable it in any Firefox version by setting this preference to <code>false</code>."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We use the "flags" directive to indicate that support (in release) is behind a flag. See the docs for more info and an example of use.
In this case, we also have to reformulate the note to say that the preference is on by default in Firefox Developer Edition and Nightly builds.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please see latest diff

@bennypowers
Copy link
Contributor Author

I'm unclear as to the correct wording for the note, assuming there's also a flags directive. Can you link to an example?

@teoli2003
Copy link
Contributor

Sure, here is the docs with an example: https://github.com/mdn/browser-compat-data/blob/master/schemas/compat-data-schema.md#flags

the "notes" could be something like: "The preference is set to <code>true</code> by default on Firefox Nightly and on Firefox Developer Edition, but not on the official release."

Copy link
Member

@Elchi3 Elchi3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

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

Labels

data:api Compat data for Web APIs. https://developer.mozilla.org/docs/Web/API

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants