You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 16, 2021. It is now read-only.
When i want to use zeroclipboard inside element which is in fullscreen mode it is not visible. On Chrome and FF when element goes into fullscreen mode its z-index is set to (2^31)-1 so when i set zeroclipboard zIndex config to the same value it works as expected. But IE11 and Edge has different approach to fullscreen - it just doesn't show any element that is outside of selected elements DOM subtree.
One way to fix that is to allow to create htmlBridge somewhere else not only as the body element exact child but that can cause problems with evaluation of absolute position. Do you have any other solutions how to fix that?
The text was updated successfully, but these errors were encountered:
In my pull request i have added "findExistingContainer" config param. If it is set to true zeroclipboard container will not be created, instead element with id set to containerId will be selected as a zeroclipboard container. This allows to place it inside the element that will be put into fullscreen mode but it may cause some problems with position evaluation in case of some complicated layouts.
When i want to use zeroclipboard inside element which is in fullscreen mode it is not visible. On Chrome and FF when element goes into fullscreen mode its z-index is set to (2^31)-1 so when i set zeroclipboard zIndex config to the same value it works as expected. But IE11 and Edge has different approach to fullscreen - it just doesn't show any element that is outside of selected elements DOM subtree.
One way to fix that is to allow to create htmlBridge somewhere else not only as the body element exact child but that can cause problems with evaluation of absolute position. Do you have any other solutions how to fix that?
The text was updated successfully, but these errors were encountered: