Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Unify checking for fullscreen availability #154

Conversation

s-h-a-d-o-w
Copy link
Contributor

screenfull now always provides an object that at least contains enabled, making a seperate check for screenfull being false unnecessary.

Fixes #142

(Sidenote: I have no access to browsers that don't support fullscreen, so I couldn't verify the functionality. You've probably already considered the following but... that's why I would suggest applying for an open source account at saucelabs and writing a test that confirms availability or lack thereof across various browsers.)

screenfull now always provides an object that at least contains
`enabled`, making a seperate check for `screenfull` being `false`
unnecessary.

Fixes sindresorhus#142
@sindresorhus sindresorhus changed the title Unifies checking for fullscreen availability Unify checking for fullscreen availability Sep 9, 2019
@sindresorhus sindresorhus merged commit 633ea78 into sindresorhus:master Sep 9, 2019
@sindresorhus
Copy link
Owner

Thanks :)

@Mister-Hope
Copy link

Mister-Hope commented May 4, 2020

I don't agree with this change , see #173 you shouldnot split an interface with { isEnabled: true } since it will case errors in every method

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document that screenfull can be false
3 participants