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

Allow any layout for amp-social-share, with test. #3099

Merged
merged 6 commits into from
May 10, 2016
Merged

Allow any layout for amp-social-share, with test. #3099

merged 6 commits into from
May 10, 2016

Conversation

powdercloud
Copy link
Contributor

Fixes #3014

@Gregable
Copy link
Member

Gregable commented May 4, 2016

LGTM

@@ -28,6 +28,7 @@
<script async src="https://cdn.ampproject.org/v0.js"></script>
</head>
<body>
<!-- a fixed-layout example (layout is implicitly fixed) -->
<amp-social-share type="pinterest" width="60" height="44">
<script type="application/json">
Copy link
Contributor

Choose a reason for hiding this comment

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

We dropped the script configuration support can we invalidate that?

- Any type is allowed, it's just a string.
- data-share-endpoint is optional. If given, it must be a URL with one
  of the whitelisted protocols. Relative URLs are not allowed.
@powdercloud
Copy link
Contributor Author

@mkhatib I updated this, as discussed. Please take another look! Thanks.

<!-- Valid: unknown type, no endpoint given
Note: It would be good to consider this invalid, but given the choices
around required / optional parameters for this tag, we don't have a
convenient way to do that. This will probablly yield a runtime error.
Copy link
Contributor

Choose a reason for hiding this comment

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

Yes. I think runtime error should be good enough. @dvoytenko what do you think?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes. I believe this should be a runtime error, not a validator error.

@mkhatib mkhatib added NEEDS REVIEW and removed LGTM labels May 9, 2016
@mkhatib
Copy link
Contributor

mkhatib commented May 9, 2016

Thanks @powdercloud!

un-LGTM for now to get @dvoytenko's input on some of the points we chatted about.

@mkhatib
Copy link
Contributor

mkhatib commented May 9, 2016

Filed #3165 to do some research on other popular app protocols. But for now this LGTM.

Thanks for getting this in! One this is in production validator we can probably turn off experiment on amp-social-share - there are few publishers asking for it.

@mkhatib mkhatib added LGTM and removed NEEDS REVIEW labels May 9, 2016
@mkhatib
Copy link
Contributor

mkhatib commented May 9, 2016

pinging @dvoytenko for a final look.

@dvoytenko
Copy link
Contributor

LGTM from me as well.

@powdercloud powdercloud merged commit dd47548 into ampproject:master May 10, 2016
@powdercloud powdercloud deleted the amp-social-share branch May 10, 2016 21:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Validator] Allow all layouts in amp-social-share
5 participants