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

Using U+2757 (heavy exclamation mark) on forms leads to inconsistent appearance across devices

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 3.2
    • 3.2
    • Themes
    • MOODLE_32_STABLE
    • MOODLE_32_STABLE
    • MDL-57177-master
    • Hide
      1. Create a course
      2. Add an external tool to the course
      3. On the external tool form, expand all the form fields and click the "Show more" link
      4. Confirm (on all browsers, on all platforms, including mobile) all the exclamation points are blue
      Show
      Create a course Add an external tool to the course On the external tool form, expand all the form fields and click the "Show more" link Confirm (on all browsers, on all platforms, including mobile) all the exclamation points are blue

    Description

      Currently we use U+2757 on forms to indicate that a form element is "advanced". This is problematic since that codepoint is part of emoji and displays differently on different devices.

      In boost, we have this style:

      .text-info, .highlight {
          color: #5bc0de!important;
      }
      

      Which is used to style the exclamation point. However if you view the forms on a phone it'll be red, since that's the colour that apple decided that emoji should be. It will look different on other phones too.

      I don't see any reason why we can't just use a regular exclamation point.

      Attachments

        Issue Links

          Activity

            People

              cameron1729 cameron1729
              cameron1729 cameron1729
              Mark Nelson Mark Nelson
              Andrew Lyons Andrew Lyons
              John Okely John Okely
              Huong Nguyen, Bas Brands, Mathew May
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                5/Dec/16