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

amp-brightcove - pass custom params and allow data-player #1909

Merged
merged 1 commit into from
Feb 10, 2016

Conversation

mister-ben
Copy link
Contributor

A few updates to amp-brightcove

  • Some publishers need to pass custom parameters through to plugins specific to their players, e.g. article-specific values that need to be included in ad tags. All data-param-* attributes will now be passed camel cased in the query string of the player iframe src, in line with Append data-param-* attributes to amp-iframe src as query params. #1537
  • Documentation for data-param-*
  • Tests for data-param-*
  • amp-brightcove uses data-player-id as an attribute whereas the standard non-AMP embed for the Brightcove Player uses data-player. data-player had been intended, hence the confusion in the docs (Brightcove player attribute #1793). Since publishers may well assume the same attribute as the non-AMP embed, amp-brightcove now supports either.
  • Docs and examples have been updated to standardise on data-player but note the compatibility with data-player-id

@dvoytenko
Copy link
Contributor

/cc @Gregable @powdercloud on any possible validator needs.

@cramforce
Copy link
Member

LGTM. Test errors seem unrelated. This should not affect validation.

Please squash the commits and this is good to go.

Allow `data-player` as intented as well as `data-playerid`
Use `data-player` in docs
Document `data-param-*`
@mister-ben
Copy link
Contributor Author

Squashed. Thanks.

cramforce added a commit that referenced this pull request Feb 10, 2016
amp-brightcove - pass custom params and allow `data-player`
@cramforce cramforce merged commit 14ff6eb into ampproject:master Feb 10, 2016
jridgewell added a commit to jridgewell/amphtml that referenced this pull request Feb 11, 2016
…htcove-params"

This reverts commit 14ff6eb, reversing
changes made to db7e7cb.
@jridgewell
Copy link
Contributor

Reverted in #1924 due to (seemingly unrelated) test failures. I'll be investigating today.

@mister-ben
Copy link
Contributor Author

It's beyond me why they're failing. Sorry for causing trouble.

@mstoltenburg
Copy link

Maybe https://github.com/ampproject/amphtml/blob/master/validator/validator.protoascii#L2212 should be changed to check for data-player-id again? Because that is used by the examples…

erwinmombay added a commit that referenced this pull request Feb 16, 2016
Revert "Revert "Merge pull request #1909 from BrightcoveOS/amp-brightcove-params""
@Gregable
Copy link
Member

Following up on this thread to make sure we're validating amp-brightcove correctly. The current rules are:
data-account - mandatory, all values allowed
data-* - optional, all values allowed
Allowed layouts: fixed, fixed_height, responsive, fill, nodisplay.

In order to help publishers find bugs, It looks like we may also want to:

  • require one of data-player or data-player-id, possibly with a deprecation warning for the latter?
  • require "default", any shortid, or any GUID for the value of data-embed, if attribute is set. What is the format of a shortid?
  • require "default" or any GUID for the value of data-embed, if attribute is set.

Thoughts?

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

Successfully merging this pull request may close these issues.

7 participants