Problem/Motivation

Postponed on #3113211: Create test for theme asset decoupling from Stable and address any regressions that decoupling may cause

Core includes the following rule for .container-inline

.container-inline div,
.container-inline label {
  display: inline-block;
}

This rule hadn't reached Umami as the Stable theme has a version of this styling with it set to display: inline; instead.
In this issue #3113211: Create test for theme asset decoupling from Stable and address any regressions that decoupling may cause, core themes no longer inherit assets from Stable. This meant that Umami got the display: inline-block; rule instead of display: inline;, which resulted in at least one regression:

(note that the search block is fine, which is the only non-admin use of .container-inline that comes to mind, but there may be others)

To prevent this regression, a rule was added to Umami's base.css with a @todo pointing to this issue
The issue #2226317: Divs in the container-inline wrapper should be inline-block instead of inline, which first made the changes, explains why there was interest in changing this rule. Umami's maintainers can determine if it's preferable to address the regressions and inherit the

.container-inline div, .container-inline label

from core, or simply keep the rule added in #2226317.

Proposed resolution

Determine if it is best to inherit the display: inline-block; style from core, or keep the display: inline; style added in #3113211

Remaining tasks

If changing the style seems unnecessary, just remove the @todo comments referencing this issue. If it would be beneficial, remove the @todo comments and the CSS accompanying it, and fix any regressions.

User interface changes

API changes

Data model changes

Release notes snippet

CommentFileSizeAuthor
#6 umami-inline-radios.PNG4.18 KBneograph734

Comments

bnjmnm created an issue. See original summary.

bnjmnm’s picture

Issue summary: View changes
bnjmnm’s picture

Title: Change container-inline rules in Bartik and Umami » Investigate changing container-inline rules
Component: CSS » Umami demo
Issue summary: View changes
Status: Active » Postponed
xjm’s picture

Status: Postponed » Active

The blocker is in.

xjm’s picture

Title: Investigate changing container-inline rules » Investigate changing container-inline rules in Umami
neograph734’s picture

I have discovered issues with RTL display of inline radio buttons when using display: inline. display: inline-block solves this. Please see #2912824: Inappropriate trailing colons in Claro and Umami.

When attempting to test that patch with Umami it appeared that this theme has no great support for inline elements anyway, as every input element has a minimum width of 100%.

inline radios

If you change the width into something smaller, one can see the items switch place in RTL languages as described in the linked issue.

I recommend using display: inline-block.

Version: 9.0.x-dev » 9.1.x-dev

Drupal 9.0.10 was released on December 3, 2020 and is the final full bugfix release for the Drupal 9.0.x series. Drupal 9.0.x will not receive any further development aside from security fixes. Sites should update to Drupal 9.1.0 to continue receiving regular bugfixes.

Drupal-9-only bug reports should be targeted for the 9.1.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.2.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.1.x-dev » 9.3.x-dev

Drupal 9.1.10 (June 4, 2021) and Drupal 9.2.10 (November 24, 2021) were the last bugfix releases of those minor version series. Drupal 9 bug reports should be targeted for the 9.3.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.