-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
✨ Bento amp-video-iframe #31055
✨ Bento amp-video-iframe #31055
Conversation
@@ -21,6 +21,29 @@ const TAG = 'amp-video'; | |||
|
|||
class AmpVideo extends VideoBaseElement {} | |||
|
|||
/** @override */ | |||
AmpVideo['props'] = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved since props vary by component, so I think they should be specified individually.
'component': VideoIframe, | ||
'onMessage': onMessage, | ||
'makeMethodMessage': makeMethodMessage, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't need a specific component, but only specific props
.
This can be the case for 3p players like amp-youtube
too, where we can specify its behavior only by changing props.
In a future world where CE get compiled away, for other components this can be expressed in one of two ways.
From:
<amp-youtube ...></amp-youtube>
Into:
A.
<Youtube ... />
or B.
<VideoIframe makeMethodMessage={YOUTUBE_MAKE_METHOD_MESSAGE} ... />
This is irrelevant for this PR, but it might be interesting to note.
…frame # Conflicts: # build-system/compile/bundles.config.js # extensions/amp-video-iframe/0.1/amp-video-iframe.js # extensions/amp-video/1.0/base-element.js # extensions/amp-video/1.0/video-wrapper.js
eb6cd4d
to
b51023c
Compare
<amp-video-iframe> that uses a Preact VideoIframe.
No description provided.