Core 9.5.0 causing broken-looking styling (Legacy widget, with Seven)

Created on 5 January 2023, over 1 year ago
Updated 13 October 2023, 9 months ago

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

  1. Use Seven theme (doesn't seem to be an issue for Claro)
  2. Edit a node with a paragraph field in it that uses the Legacy widget
  3. 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.
  4. Then either:
    1. 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
    2. 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

๐Ÿ› Bug report
Status

Fixed

Version

1.15

Component

User interface

Created by

๐Ÿ‡บ๐Ÿ‡ธUnited States maxstarkenburg

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.69.0 2024