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

Fullscreen not fullscreen with transform parent element #13

Open
macsupport opened this issue Jun 20, 2018 · 4 comments
Open

Fullscreen not fullscreen with transform parent element #13

macsupport opened this issue Jun 20, 2018 · 4 comments

Comments

@macsupport
Copy link

I'm using flickity fullscreen within a card in a uikit masonry grid ( I know, I should use yours...) and getting this odd behavior. When trying to open a full screen flickity carousel, it opens within the card div inside the grid not fullscreen in the grid itself, so I get a "mini fullscreen flickity". Any flickity fullscreen option to bypass this annoying behavior, I.e choose body or a class to open flickity in?

Heres the codepen

@desandro desandro changed the title Fullscreen not fullscreen when used inside a uikit masonry grid Fullscreen not fullscreen with transform parent element Jun 27, 2018
@desandro
Copy link
Member

Thanks for reporting this issue. Looks like because uikit Masonry uses CSS transforms for positioning, a child element with position: fixed will use that transformed parent element for its fixed position, not the body. Hey, I didn't know that one either.

@MrChriZ
Copy link

MrChriZ commented Jul 20, 2018

I've just ran into this issue but using Liquid Fire from an Ember Application.
Possibly linked to this issue? ember-animation/liquid-fire#597

The Liquid container leaves a translate on the container div.

@macsupport
Copy link
Author

I'm assuming this is not fixable at this point?

@desandro
Copy link
Member

As this is a browser rendering issue, the fix would be to change whatever library is using transform to position: absolute with left, top.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants