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 issue with Chrome 67+ #111

Merged
merged 1 commit into from
Sep 4, 2018

Conversation

dheerajkumarmadaan
Copy link
Contributor

…D_INPUT anymore. Refactored code to pass empty object if ALLOW_KEYBOARD_INPUT is not found.

@sindresorhus
Copy link
Owner

sindresorhus commented Aug 26, 2018

In Chrome 68, document.body.webkitRequestFullScreen(Element.ALLOW_KEYBOARD_INPUT) works fine, so I'm not sure what the issue actually is?

@dheerajkumarmadaan
Copy link
Contributor Author

screen shot 2018-08-27 at 1 50 38 pm

I tried demo page on chrome 68 and found this error. It is reproducible on multiple system, I can see it is working on some other chrome 68 as well. Not sure what 's the special settings that you need to turn on your chrome to reproduce this.

Assume you cannot reproduce this but below line is still buggy:

elem[request](keyboardAllowed && Element.ALLOW_KEYBOARD_INPUT);
Let say keyboardAllowed is false so this method would be invoked with:
elemrequest
i.r webkitRequestFullScreen(false)

But this method takes object as an argument and it will throw error as specified in screen shot.
This PR will handle this case.

@dheerajkumarmadaan
Copy link
Contributor Author

screen shot 2018-08-27 at 1 58 06 pm

@sindresorhus
Copy link
Owner

I cannot reproduce this on either 68.0.3440.106 or 70.0.3534.0 on macOS. Which exact Chrome version are you on? It might have been fixed in a minor v68 version.

@dheerajkumarmadaan
Copy link
Contributor Author

I am on 68.0.3440.106
screen shot 2018-08-27 at 2 49 38 pm

@sindresorhus
Copy link
Owner

sindresorhus commented Aug 27, 2018

I don't like changing something I cannot reproduce, but alright. Please remove the dist changes. This will be generated on release.

@dheerajkumarmadaan
Copy link
Contributor Author

Ok.. Removed dist folder changes for screenfull.js

@sindresorhus
Copy link
Owner

There's still a diff for dist/screenfull.min.js

@amccloud
Copy link

@dheerajkumarmadaan @sindresorhus I’m able to reproduce with the same browser/os

Adding error text to this issue so other people can search for it.

TypeError
Failed to execute 'requestFullscreen' on 'Element': parameter 1 ('options') is not an object.

@salilk
Copy link

salilk commented Aug 29, 2018

@dheerajkumarmadaan @sindresorhus @amccloud -- I’m also able to reproduce the issue. Looking at the PR - the fix looks good as well as safe. Thanks!!

…D_INPUT anymore. Refactored code to pass empty object if ALLOW_KEYBOARD_INPUT is not found.
@dheerajkumarmadaan
Copy link
Contributor Author

dheerajkumarmadaan commented Aug 30, 2018

@sindresorhus I just removed dist folder changes.

cagen added a commit to ShimoFour/screenfull.js that referenced this pull request Aug 31, 2018
cagen added a commit to ShimoFour/screenfull.js that referenced this pull request Aug 31, 2018
@sindresorhus sindresorhus changed the title Fixed screenfull issue in chrome 67 as it does not have ALLOW_KEYBOAR… Fix issue with Chrome 67+ Sep 4, 2018
@sindresorhus sindresorhus merged commit 04f9ec4 into sindresorhus:gh-pages Sep 4, 2018
PanJiaChen added a commit to PanJiaChen/vue-element-admin that referenced this pull request Sep 6, 2018
AngusFu added a commit to AngusFu/brand-player that referenced this pull request Sep 12, 2018
SEE sindresorhus/screenfull#111 
Fix issue with Chrome 67+
SidKH added a commit to SidKH/screenfull.js that referenced this pull request Sep 13, 2018
@shuodashen
Copy link

I can reproduce this issue on Chrome Canary, which version is : 72.0.3616.0 (Official Build) canary (64-bit).
Since this commit is merged, I will upgrade to the latest version and try again.

JsAppNinja added a commit to JsAppNinja/vue-vuex-adminpage that referenced this pull request Jan 25, 2019
@joedf
Copy link

joedf commented Mar 27, 2019

Updating to from v3.3.2 - 2017-10-27 to v4.1.0 - 2019-03-19 worked for me! 👍

ninjadevtrack added a commit to ninjadevtrack/vue-vuex-admin that referenced this pull request Dec 24, 2019
tocaata pushed a commit to tocaata/qemu-admin that referenced this pull request Jun 2, 2020
iGuru-T added a commit to iGuru-T/vue-element-admin that referenced this pull request Mar 22, 2022
B-Guru added a commit to B-Guru/vue-element-admin that referenced this pull request Mar 24, 2022
CoinDev1121 added a commit to CoinDev1121/vue-element-admin that referenced this pull request Apr 4, 2022
coin-monster added a commit to coin-monster/vue-element-admin that referenced this pull request May 24, 2022
anteroselin added a commit to anteroselin/vue-element-admin that referenced this pull request Mar 6, 2023
phantomeco pushed a commit to phantomeco/vue-element-admin that referenced this pull request Jun 25, 2023
trent081 added a commit to trent081/admin-dashboard-vue that referenced this pull request Sep 1, 2023
FPLeader added a commit to FPLeader/vue-element-admin that referenced this pull request Sep 12, 2023
harrialeksi pushed a commit to harrialeksi/Vue-admin that referenced this pull request Sep 13, 2023
fuyuooumi1027 added a commit to fuyuooumi1027/vue-element-admin that referenced this pull request Nov 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants