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
Chonky calculates the context menu position incorrectly if it is placed inside components that use css transform.
(For elements whose layout is governed by the CSS box model, any value other than none for the transform property also causes the element to establish a containing block for all descendants. Its padding box will be used to layout for all of its absolute-position descendants, fixed-position descendants, and descendant fixed background attachments.)
I tried to override the built in OpenFileContextMenu definition to adjust the position as said in the documentation (These are the file actions Chonky requires to function correctly. They are always enabled, and there is no way to disable them. If you know what you are doing, you can override an essential file action by defining a custom file action with the same action ID.). But I don't see any reaction on adding Custom action with ChonkyActions.OpenFileContextMenu.id. The built in one keep triggering.
Is there way to fix this bug or at least allow to adjust OpenFileContextMenu action?
The text was updated successfully, but these errors were encountered:
Chonky calculates the context menu position incorrectly if it is placed inside components that use css transform.
(For elements whose layout is governed by the CSS box model, any value other than none for the transform property also causes the element to establish a containing block for all descendants. Its padding box will be used to layout for all of its absolute-position descendants, fixed-position descendants, and descendant fixed background attachments.)
I tried to override the built in OpenFileContextMenu definition to adjust the position as said in the documentation (These are the file actions Chonky requires to function correctly. They are always enabled, and there is no way to disable them. If you know what you are doing, you can override an essential file action by defining a custom file action with the same action ID.). But I don't see any reaction on adding Custom action with ChonkyActions.OpenFileContextMenu.id. The built in one keep triggering.
Is there way to fix this bug or at least allow to adjust OpenFileContextMenu action?
The text was updated successfully, but these errors were encountered: