Edge Strange Character Issue with Custom Font in br tags

Not reproducible Issue #10160748


Tiuser L.
Dec 12, 2016
This issue is public.
Reported by 5 people

Sign in to watch or report this issue.

Steps to reproduce

There is a weird issue where the space gylph of the custom font is rendered at the <br> tags (rendered even if using “<br/><br/>” with no spaces)

  1. Create a html file
  2. Create a @font-face declaration for a custom font with single character EEB8.
  3. Add unicode-range css property to only apply for custom font for U+EEB8-F12B.
  4. In the body tag, add some <br/> tags
  5. View the html file in IE Edge
    For some reason, there is a box glyph shown at where the <br> tags are. Further investigation reveals that these boxes refer to the space character in the custom font (tried adding a gylph for space character (U+0020) for the custom font and the box changes to what the space character is using). Note that the space characters in the paragraph text are not rendered as boxes.

Please check sample test case at http://basic.orionhub.org:8000/test.html

Screenshot of the issue encountered: https://www.dropbox.com/s/83xfga9tgemgdm1/screendumpIEEdge.png?dl=0

Attached the files used in the sample test case.

System Information:
Microsoft Edge version is 38.14393.0.0
Microsoft EdgeHTML 14.14393
Windows 10 Pro edition 64 bit

Can you please confirm/advise if this is an IE/Edge bug as unicode-range seems to be partially supported only (based from caniuse.com/#feat=font-unicode-range).

(our client needs confirmation on this)

Thank you


Comments and activity

  • Above issue doesn’t appear in FF and Chrome

  • Microsoft Edge Team

    Changed Assigned To to “Ibrahim O.”

    Changed Assigned To to “Rick J.”

    Changed Assigned To to “Christian F.”

  • Sorry, it seems I used the wrong .woff file (with space character gylph in custom font file) I updated .woff file hosted in http://basic.orionhub.org:8000/HKELCustomFont.woff to not have the space character defined.

  • Hello, would like to followup on any updates.


  • We have the same problem at my company.

    A custom web font that renders some multi-line text using
    to force line breaks at certain points causes Edge to render an ! (exclamation mark) (hexcode 0x21) just before the

    still happens, it just insert the extra glyph for some reason.

    Any update on this bug?

    Link to example (unzip anywhere):

    How to reproduce:

    1. Unpack the zip
    2. Open the index.html in Edge or IE11
    3. Notice the extra exclamation points at the end of each line and on empty lines.

    Should render as it does in Chrome or FireFox.

    Edge introduces extra character for each

    Try to select the text. When you do, some of the exclamations points stop rendering (but not all).

  • The zip has also been uploaded as an attachment to this bug.

  • Microsoft Edge Team

    Changed Status to “Not reproducible”

  • Hey folks, this issue is not reproing on internal builds, I have uploaded an attachment of no-repro-10160748.png that shows Edge 17 side by side with Edge 18 using Daniel’s files. As such resolving as fixed. If you are on an insiders build please verify that your issue is addressed, I am following this issue so even if it is resolved I will get emails with the comments. Thank you for reaching out.

  • That is good news. Thanks Greg!

    Any information about what fixed the bug and whether this fix will be applied to IE11?

    PS. Is the official bug resolution “fixed” or "cannot reproduce"? ;)

You need to sign in to your Microsoft account to add a comment.

Sign in