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

folder_contents Configure display column dialog half visible #3124

Closed
vincentfretin opened this issue Jun 19, 2020 · 9 comments
Closed

folder_contents Configure display column dialog half visible #3124

vincentfretin opened this issue Jun 19, 2020 · 9 comments

Comments

@vincentfretin
Copy link
Member

BUG/PROBLEM REPORT (OR OTHER COMMON ISSUE)

What I did:

Create a Plone site in German
Go in folder contents, click on "Configure display column"

What I expect to happen:

The dialog should be completely visible.

What actually happened:

The dialog is half visible, some part is below the toolbar
Capture d’écran de 2020-06-19 11-58-36

This is what it looks like in English:
Capture d’écran de 2020-06-19 12-01-20

What version of Plone/ Addons I am using:

Plone 5.2.1

@vincentfretin
Copy link
Member Author

vincentfretin commented Jun 20, 2020

When I put plone-editor-tools bundle js in develop mode, the issue is fixed!
So the issue was surely fixed by someone, but the bundle wasn't rebuild?

@vincentfretin
Copy link
Member Author

The question now is how to build this bundle to include it in a new release? I don't have a clue. Someone knows?

@vincentfretin
Copy link
Member Author

To create the new bundles, the documentation is at https://github.com/plone/plone.staticresources

@vincentfretin
Copy link
Member Author

vincentfretin commented Jun 21, 2020

The bundles have been updated recently by @thet last_compilation 2020-06-16 10:10:00
and I see in plone.staticresources package.json with the latest commit of mockup master https://github.com/plone/mockup.git#e6bd1977871c7dbeb75b0eccc395687320e681b8

Huh, now I played a little bit with plone.staticresources it appears this is not an issue with released vs develop mode, weird. I can reproduce the issue in develop mode. The issue is not existing in plone.staticresources 1.2.1, it only occurs on master.

We have those CSS rules:

http://0.0.0.0:8080/Plone/++plone++static/++unique++2020-06-21%2010%3A20%3A26.676322/src/plone.staticresources/src/plone/staticresources/static/components/bootstrap/less/popovers.less
.pat-structure .popover {
 z-index: 1060;
}

http://0.0.0.0:8080/Plone/++plone++static/++unique++2020-06-21%2010%3A20%3A26.676322/src/mockup/mockup/patterns/structure/less/pattern.structure.less
.pat-structure .navbar, .pat-structure .pat-structure .navbar {
 z-index: 10;
}

toolbar is z-index: 20

This is what changed, in the DOM, now we have:

<div class="navbar ui-offset-parent>
  <div id="popover-structure-columns" class="popover attribute-columns ui-offset-parent active bottom">
  </div>
</div>

And before we had

<div class="navbar ui-offset-parent></div>
<div id="popover-structure-columns" class="popover attribute-columns ui-offset-parent active bottom"></div>

@vincentfretin
Copy link
Member Author

vincentfretin commented Jun 21, 2020

Capture d’écran de 2020-06-21 10-31-43
Capture d’écran de 2020-06-21 10-32-57

@vincentfretin
Copy link
Member Author

I couldn't find what changed in the js to have a different DOM like this.
The issue can be fixed by changing the CSS rule for .pat-structure .navbar from z-index: 10 to z-index: 1060. I'm not sure if this can lead to other regressions somewhere else.

@vincentfretin
Copy link
Member Author

I did the css fix there plone/mockup@a6fa639
waiting merge of plone/mockup#986

@vincentfretin
Copy link
Member Author

This issue was a regression because of plone/mockup#964
The z-index of children is only applied within the same stacking context, see
https://coder-coder.com/z-index-isnt-working/
for more details.

@vincentfretin
Copy link
Member Author

The fix I did included in mockup 3.2.0 did regressions with submenu in Plone toolbar and portal tabs subtrees simlar to #2307 that was actually fixed before.
My new PR plone/mockup#1002 revert the previous fix and fix this issue in a different way.

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

No branches or pull requests

1 participant