Inappropriate trailing colons in Claro and Umami

Created on 29 September 2017, about 7 years ago
Updated 14 December 2023, about 1 year ago

Problem/Motivation

A follow-up from #2236789: Styling of inline radios broken: inappropriate trailing colons (breaks EditorImageDialog) β†’ for the bug in classy of having colons on radio buttons through classy.
This will be an issue for any using .container-inline CSS that originated from Classy (most easily verfied by it being in a themes /classy subdirectory).

Proposed resolution

Remove colons from radio button labels in .container-inline inline containers.

Remaining tasks

User interface changes

No more colons on radio button labels in inline containers and any additional style changes that are necessary for this change to look right within a form.

Steps to reproduce

Reproducing requires having a radios field inside an element with the .container-inline class. In Drupal 10, the only forms that have this out of the box are deprecated and CKEditor 4 specific, so it's probably easier to manually create a form with a radios element wrapped in .container-inline, or just manually add the .container-inline class with browser developer tools.

Despite it not appearing anywhere in core currently, the .container-inline wrapper does need to properly support any field type as contrib could be making use of container-inline form elements with radios.

API changes

πŸ› Bug report
Status

Needs work

Version

11.0 πŸ”₯

Component
CSSΒ  β†’

Last updated 10 days ago

Created by

πŸ‡¨πŸ‡¦Canada joelpittet Vancouver

Live updates comments and jobs are added and updated live.
  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

  • CSS

    It involves the content or handling of Cascading Style Sheets.

  • Needs screenshots

    The change alters the user interface, so before and after screenshots should be added to document the UI change. Make sure to capture the relevant region only. Use a tool such as Aviary on Windows or Skitch on Mac OS X.

  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

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.

  • πŸ‡ΊπŸ‡ΈUnited States bnjmnm Ann Arbor, MI

    Confirmed this is still happening in Claro/Umami (did not test Olivero). I added steps to reproduce in the IS. The only core instance of this seems to be in deprecated CKEditor 4 related forms, but this issue should remain open since .container-inline should fully support all core form elements, even if they don't happen to appear in an inline form.

    This requires some extra steps to reproduce so I'm not sure what kind of momentum this issue will have going forward, but the problem still exists

  • Status changed to Needs work almost 2 years ago
  • The Needs Review Queue Bot β†’ tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".

    Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

    Consult the Drupal Contributor Guide β†’ to find step-by-step guides for working with issues.

  • @pameeela opened merge request.
  • Status changed to Needs review almost 2 years ago
  • πŸ‡¦πŸ‡ΊAustralia pameeela

    Made an updated MR with the changes from #2912824-22: Inappropriate trailing colons in Claro and Umami β†’ just applied to the current core themes.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Wonder if this will require a simple test case to check if the colon is there or not. Or is that overkill?

  • Status changed to Needs work almost 2 years ago
  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Posted to #bugsmash and @mstrelan commented

    The colon is never really there. I'm not sure if we can even check pseudo-elements? Either way I think PHP should trust that CSS is doing CSS things, it would be more appropriate to check that PHP / twig is outputting the appropriate markup so CSS can style it accordingly. That may already exist?

    So since this is pure css don't think we need tests then.

    But there was a CI failure in the MR.

    Hiding the files as the work is being done in the MR now.

  • Status changed to Needs review almost 2 years ago
  • πŸ‡¦πŸ‡ΊAustralia pameeela

    Oops! Fixed.

  • Status changed to RTBC almost 2 years ago
  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Thanks!

  • Status changed to Needs work over 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States bnjmnm Ann Arbor, MI

    Changes requested in MR.

    Also, lets celebrate that this is the rare occasion where I'm tagging "needs screenshots" instead of wearily pointing out there are too many of them. There should be shots for Claro and Umami with checkboxes and radios.

  • First commit to issue fork.
  • Status changed to Needs review over 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States rpayanm

    Please review.

  • Status changed to Needs work over 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Threads appear to be answered

    Moving to NW per #39 for screenshots and issue summary update please.

  • πŸ‡ΊπŸ‡ΈUnited States bnjmnm Ann Arbor, MI

    I mentioned earlier that the Claro solution was using selectors that don't exist in Claro. It looks like the Claro changes were removed entirely, when the solution should be changing them to the correct selector.

  • πŸ‡³πŸ‡±Netherlands arantxio Dordrecht

    Because the merge request is currently not mergeable I've created a new patch that applies to D10.1.x

Production build 0.71.5 2024