Make the use of the indented-class consistent

Created on 14 April 2015, about 10 years ago
Updated 29 May 2025, 2 days ago

Follow-up to #2408513: Refactor forum module CSS files inline with our CSS standards β†’

Problem/Motivation

There is a inconsistency in how the .indented class is being used across modules and themes.

Proposed resolution

We create a couple of generic classes like this:

.indented {
  margin-left: 20px; /* LTR */
}
[dir="rtl"] .indented {
  margin-left: 0;
  margin-right: 20px;
}
.indented-double {
  margin-left: 40px; /* LTR */
}
[dir="rtl"] .indented-double {
  margin-left: 0;
  margin-right: 40px;
}

This way, modules can use these classes to give indentation to their elements.

Beta phase evaluation

<!--Uncomment the relevant rows for the issue. -->
πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

CSS

Created by

πŸ‡§πŸ‡ͺBelgium MathieuSpil

Live updates comments and jobs are added and updated live.
  • 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.

  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

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 smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024