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-ima-video: hideControls() does not fully hide controls #20787

Open
alanorozco opened this issue Feb 12, 2019 · 3 comments
Open

amp-ima-video: hideControls() does not fully hide controls #20787

alanorozco opened this issue Feb 12, 2019 · 3 comments

Comments

@alanorozco
Copy link
Member

alanorozco commented Feb 12, 2019

#20760 introduces support for <amp-ima-video dock>. In docked mode, custom mini controls are displayed. Even though docking requested ima-video to hideControls, the latter will still display them when the video is paused, effectively showing two sets of controls at a time.

This can be approached in one of two ways:

  1. Honor the result of dynamic hideControls to hide them regardless of playing state. I don't believe this would break any use-cases, since hideControls calls are dynamic and should in theory be superseded by showControls when the calling module requires it. This may require slight amp-ima-video refactoring (maybe) and additional internal postMessage APIs (doubtful).

  2. Support force in hideControls. This has the unfortunate side-effect of having to backfill all players to support this parameter. This would still require additional changes to amp-ima-video, including necessary postMessage API changes to pass the flag through. However, flags like force should generally be avoided, so I'm not in favor of this API unless, for some reason, amp-ima-video UX requires decoupling of hiding use-cases (unlikely).

/to @torch2424
/cc @aghassemi

@torch2424
Copy link
Contributor

torch2424 commented Feb 12, 2019

Also adding @curseagain , in case you are interested in picking this up (Would improve video docking support if your team is interested in that). 😄

@ampprojectbot ampprojectbot added this to the New FRs milestone Feb 13, 2019
@torch2424 torch2424 added this to To Do in Ads & Analytics Fixit - April 2019 via automation May 2, 2019
@calebcordry calebcordry added this to Needs triage in Ads & Analytics issue triaging via automation Jul 2, 2019
@lannka lannka moved this from Needs triage to Triaged in Ads & Analytics issue triaging Jul 3, 2019
@curseagain
Copy link
Member

Hello all! Somehow I missed this, but I'll pick this ticket up next. Thanks!

@lannka lannka assigned calebcordry and unassigned torch2424 Jan 9, 2020
@stale
Copy link

stale bot commented Sep 17, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

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