youtube-player startSeconds and endSeconds not working

[taivo]

Reproduction

Steps to reproduce:

1. Create a wrapper component that uses , just like the example in the docs except with startSeconds and endSeconds

<youtube-player width="100%" height="100%" 
    videoId="PRQCAL_RMVo" 
    [startSeconds]="40" 
    [endSeconds]="60"
</youtube-player>

2. Observe that the startSeconds and endSeconds parameters were not respected. Clicking the play button shows video starting at 0 second.

Expected Behavior

What behavior were you expecting to see?
I expected to see the video start playing at the 40 second mark.

Actual Behavior

This method

set startSeconds(startSeconds) {
      this._startSeconds.emit(startSeconds);
}

fired before this line in YouTubePlayer.ngOnInit

const startSecondsObs = this._startSeconds.pipe(startWith(undefined));

The same is true for endSeconds and suggestedQuality.

The effect is that the initial startSeconds and endSeconds value specified by the wrapper component is reset to undefined

For example: if the template was

<youtube-player width="100%" height="100%" 
    videoId="PRQCAL_RMVo" 
    [startSeconds]="40" 
    [endSeconds]="60"
</youtube-player>

The property startSeconds will trigger this._startSeconds.emit(40);, then startSecondObs will be set to startWith(undefined), and from there on, the initial values 40 and 60 no longer honored.

Work around: in the component that uses , use template variables to keep track of startSeconds, endSeconds, and suggestedQuality, and leverage setTimeout or lodash.defer to set those values a 2nd time.

---

Glancing at the code, I believe the correct approach has been handled for videoId, width, and height. It just has not been propagated to startSeconds, endSeconds, and suggestedQuality.

Environment

• Angular:
• CDK/Material:
• Browser(s):
• Operating System (e.g. Windows, macOS, Ubuntu):

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}