Suggestion for an <amp-embed> builtin tag#1607
Conversation
src/custom-element.js
Outdated
There was a problem hiding this comment.
Do we need the state right now?
There was a problem hiding this comment.
We are not using it in this iteration, thought it might be useful to keep.
|
@powdercloud Could you take a look at the validator changes? |
|
@nitzanvolman Please add one usage to the |
|
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed, please reply here (e.g.
|
71290a1 to
8f2ae06
Compare
|
@cramforce |
|
@nitzanvolman The validation error for brightcove was just fixed (This is actually the point of the test. It found an actual error :) Will take another look |
There was a problem hiding this comment.
Rebase and then make another entry (2nd regex) for your specific error.
|
@nitzanvolman Just some tiny comments. Please rebase and squash commits. @Gregable @powdercloud Could you take a look at the validator change. |
validator/validator.protoascii
Outdated
There was a problem hiding this comment.
Please add a comment here and with amp-ad that changes should be reflected in the other respectively.
There was a problem hiding this comment.
@powdercloud since i will be removing shortly this from this PR as per your instructions, i think this comment above should be directed to you.
should add a comment that future changes on amp-ad should be done on amp-embed and vice versa.
There was a problem hiding this comment.
Yes thank you I did that - this is the (merged) commit:
679e684
|
For the validator.protoascii, I'd like to grab it and apply it internally, then propagate it to github; so the best way in this change is to leave it out. Reason being, we need to rev the revision id and if we make changes in both places we'll get conflicts, so it is more convenient that way. It looks fine in spirit though, and thanks much for understanding. |
13aebe2 to
0f58b55
Compare
…ed test-amp-ad to test agains amp-embed as well
0f58b55 to
893e58c
Compare
|
@cramforce i believe this is it. please let me know if you see that i missed anything. |
|
I signed it! |
|
LGTM |
Suggestion for an <amp-embed> builtin tag
relates to issue #1527
amp-embedaims to solve the use case of embeddable elements that have similar functional requirements asamp-ad, but it would not be semantically correct to use amp-ad. (e.g. organic content recommendations)the suggestion is to implement
amp-embedas alias foramp-ad