Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-42853

Wrong alignment for modules on frontpage in RTL in Clean

XMLWordPrintable

    • MOODLE_25_STABLE, MOODLE_26_STABLE
    • MOODLE_24_STABLE, MOODLE_25_STABLE, MOODLE_26_STABLE
    • MDL-42853-master
    • Hide
      1. Test in both Standard and Clean:
      2. Add some modules to the frontpage
      3. On the front page, make sure there is no unexpected margin/padding to the section in LTR or RTL.
      4. For master, make sure that the padding/margin between the "Edit title" icon and the activity name is consistent between RTL and LTR (and looks good) - front page + course page
      Show
      Test in both Standard and Clean: Add some modules to the frontpage On the front page, make sure there is no unexpected margin/padding to the section in LTR or RTL. For master, make sure that the padding/margin between the "Edit title" icon and the activity name is consistent between RTL and LTR (and looks good) - front page + course page

      ul, ol {    margin: 0 0 10px 25px;    padding: 0;}
      .site-topic ul.section, .course-content ul.section {    margin: 1em;}
      

      The second statement balances the margins and no RTL rule is needed.
      But it does not apply to frontpage because it should be 'sitetopic' and not 'site-topic'

      which makes modules lists on frontpage be padded on the wrong side in RTL.

      Also the padding/margin of the "Edit title" icon is on the wrong size.

        1. ss3.png
          ss3.png
          6 kB
        2. ss4.png
          ss4.png
          6 kB

            fred Frédéric Massart
            marina Marina Glancy
            Marina Glancy Marina Glancy
            Sam Hemelryk Sam Hemelryk
            Michael de Raadt Michael de Raadt
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.