Problem/Motivation
Because of the change for #3223061: Long custom block name forces 'Place block' button out of place released in 9.5.0 (and higher), I'm seeing off-looking button placement like this:

or this:

after test-driving the core update. This is due to .js td .dropbutton-multiple .dropbutton-widget { position: absolute; } now being newly more specific in core/misc/dropbutton/dropbutton.css (used to be .js td .dropbutton-widget) than .js .field--widget-entity-reference-paragraphs .dropbutton-widget { position: relative; } in paragraphs.admin.css.
Steps to reproduce
- Use Seven theme (doesn't seem to be an issue for Claro)
- Edit a node with a paragraph field in it that uses the Legacy widget
- Make sure "Hide row weights" isn't on (i.e. drag-and-drop is enabled, i.e. the "Show row weights" link is visible), as this also doesn't seem to be an issue then.
- Then either:
- if you're editing an existing paragraph, and the widget's "Edit mode" is set to "Closed" or "Preview", I think you'll already see something like the first screenshot
- Otherwise, start to "Remove" the paragraph and you should see something like the second paragraph
Proposed resolution
I assume an easy/quick/good-enough fix would be to make the particular paragraphs selector using position: relative more specific. Though I haven't read the full thread at #3223061: Long custom block name forces 'Place block' button out of place to know if perhaps a different solution for that issue might be a better/possible approach (and perhaps less prone to a specificity war?).
Remaining tasks
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #20 | 3331203-20.patch | 444 bytes | jheinon_finland |
| #11 | 3331203-11.patch | 368 bytes | lmoeni |
| #3 | core-absolute-position-affecting-paragraphs-3331203-3.patch | 364 bytes | maxstarkenburg |
| #2 | 3331203-2.patch | 522 bytes | colorfield |
| Screen Shot 2023-01-05 at 1.33.41 AM.png | 71.71 KB | maxstarkenburg |
Issue fork paragraphs-3331203
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
colorfieldNot sure if this should be the responsibility of this module, but here is a first hotfix.
Comment #3
maxstarkenburgThanks, @colorfield, I too had spun up a local patch for this (so as to not further prevent my core upgrade), which I 100% admit is rather silly with that semi-random div in it, but is perhaps a bit simpler selectors-wise (was originally going to throw in
.dropbutton-multipleà la the core change, but then realized the paragraphs position:relative might be needed for other non-multiple widgets, so just went with something simple if a bit silly/non-specific).Comment #4
3liApplying the css patches moved button placements back to where was expected.
Comment #5
leksat commentedRTBC++
Comment #6
robbdavis commentedThis is also broken with adminimal theme. Patch #3 fixes the issue.
Comment #7
eugen zerrCan also confirm the error using
* Drupal » 9.5.1
* PHP » 8.1
* Admin. theme » Adminimal
Comment #8
dydave commentedHi everyone,
Thanks a lot for raising this issue and for contributing a patch.
We would like to gladly confirm the patch from #3 fixed the issue in our case and was successfully tested on D9 with:
9.5.21.15.08.11.6.0Additionally, this was also tested successfully on D10 with:
10.0.21.15.08.11.6.0+ D10 patch1.0.0-alpha1Any additional feedback, comments or reviews would be greatly appreciated.
Thanks again very much for your contributions.
Comment #9
drupalfan2 commentedSame problem here. Patch #3 helps.
Comment #10
msbtterswrth commentedRTBC++
Confirmed works for us.
* Drupal » 9.5.1
* PHP » 8.1
* Admin. theme » Seven
Comment #11
lmoeniThe patch did not work for me, I had to add a div to make it a little bit more specific.
I added a patch in case someone has the same issue.
Comment #14
joaopauloscho commentedThe patch #11 works for us on 9.5.5 - Thanks!
Comment #15
nicklasmf commentedPatch #11 works here as well on Core 9.5.5
Comment #16
thomaswalther commentedPatch #11 works also with core 9.5.8
Comment #18
berdirCommitted. I do recommend you consider switching to the recommended widget. We will eventually remove the legacy version if it becomes too much of a burden to maintain.
Comment #20
jheinon_finland commentedGreetings!
This problem is still apparent in the latest version for the Paragraphs module, 1.16. Here is the updated version of the patch.