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

fix(FEC-14172): overlay-active is not removed from player #950

Merged
merged 1 commit into from
Sep 29, 2024

Conversation

lianbenjamin
Copy link
Collaborator

Description of the Changes

bugfix

Issue:
overlay-active class is not being removed from the player, which prevents any user interaction with the player.
in this specific case, welcomeScreen of quiz is an Overlay component but is not rendered under OverlayPortal - which breaks the current condition to remove the overlay-active class.

Fix:
add a new prop - dontCheckOverlayPortal, which indicates whether Overlay should go through the OverlayPortal condition, or simply remove overlay-active class unconditionally.

Resolves FEC-14172

related pr: kaltura/playkit-js-ivq#136

@lianbenjamin lianbenjamin merged commit 11e44c6 into master Sep 29, 2024
11 checks passed
lianbenjamin added a commit to kaltura/playkit-js-ivq that referenced this pull request Sep 29, 2024
pass new prop to `Overlay` component in `welcomeScreen` component - `dontCheckOverlayPortal`, which tells `Overlay` component to not check `overlayPortal` when removing `overlay-active` class, since it is being rendered outside of overlayPortal area.

**NOTE:** left a TODO note to check why the `Overlay` is not being rendered under `OverlayPortal`, as we usually do.

Resolves [FEC-14172](https://kaltura.atlassian.net/browse/FEC-14172)
related pr: kaltura/playkit-js-ui#950

[FEC-14172]: https://kaltura.atlassian.net/browse/FEC-14172?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants