Skip to content

append coverSlip to fullscreen element instead of body #4317

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

Closed
wants to merge 2 commits into from

Conversation

FlorianMaak
Copy link

Resolves #4259

This PR checks if there is a fullscreen element and appends dragelements coverSlip to this element instead of documents body.

@alexcjohnson
Copy link
Collaborator

Thanks @FlorianMaak! But it looks to me as though the unprefixed fullscreenElement is not yet available everywhere - perhaps only 45%? In some of our other packages we use fscreen to normalize this.

@etpinard
Copy link
Contributor

Thanks very much for the PR @FlorianMaak - beyond browser support, it would be nice to write a test in the dragelement_test.js suite to lock down your fix. Would be interested in attempting to write a test?

@etpinard etpinard added status: in progress bug something broken labels Oct 29, 2019
@FlorianMaak
Copy link
Author

Sure. Going to migrate to fscreen and add tests as soon, as I'm at office tomorrow.

@FlorianMaak
Copy link
Author

Relating Tests: I think, we need to edit the karma config to work with fullscreen. Per default karma does not support fullscreen mode :/

karma-runner/karma#2292

@etpinard
Copy link
Contributor

I think, we need to edit the karma config to work with fullscreen. Per default karma does not support fullscreen mode :/

Right, writing a "real" test for fullscreen might be difficult and quite frankly not necessary.

That said, if should be possible to test the new logic using jasmine spies.


I'll be offline for the next two weeks, but @archmoj should be able to help you out if you run into problems.

@etpinard
Copy link
Contributor

... and as for the failing tests. Merging master post #4321 should make them go green ✅ again. Sorry for the inconvenience

@archmoj
Copy link
Contributor

archmoj commented Jun 3, 2020

@FlorianMaak could you please merge master into this branch and resolve the conflict?

@gvwilson gvwilson self-assigned this Jun 10, 2024
@gvwilson
Copy link
Contributor

This pull request has been sitting for a while, so I would like to close it as part of our effort to tidy up our public repositories. I've assigned it to myself to keep track of it; I'll wait until 2024-06-17 for someone to say it's still relevant and they'll to take it on, and otherwise I will close it then. Thanks - @gvwilson

@gvwilson gvwilson removed their assignment Aug 2, 2024
@gvwilson gvwilson added community community contribution fix fixes something broken P2 considered for next cycle and removed status: has TODOs bug something broken labels Aug 8, 2024
@gvwilson gvwilson closed this Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community community contribution fix fixes something broken P2 considered for next cycle
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rangeslider not working in fullscreen
5 participants