Edge hyphenation bug (CSS3)

Issue #7962380 • Assigned to Bogdan B.

Details

Author
Mateusz O.
Created
Jun 22, 2016
Privacy
This issue is public.
Reports
Reported by 4 people

Sign in to watch or report this issue.

Steps to reproduce

https://jsfiddle.net/45hLjt3v/1/](https://jsfiddle.[https://jsfiddle.net/45hLjt3v/1/](https://jsfiddle.net/45hLjt3v/1/)

 

There’s a bug in Edge concerning one of the features of the CSS3: automatic hyphenation. Edge hyphenates words only if the language of the webpage is the same as the language version of the underlying OS. This is highly impractical in modern world: many users browse pages in more than one language. Hyphenation rules should be built-in the Edge to display properly any webpage, regardless of the Windows language version. As far as I’m concerned, that’s the way Firefox handles this issue – by having hyphenation rules for all languages built-in. I attached a screenshot illustrating the issue.

To reproduce a bug, we’ll simply create a simple index.html document…

<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="UTF-8"> 
<link rel="stylesheet" href="styles.css">
</head>
<body>
<p>Sample long text in English[…]<\p>
<\body>
<\html>

…with the following CSS sheet called styles.css:

p {
-webkit-hyphens: auto;
-moz-hyphens: auto;
-ms-hyphens: auto;
hyphens: auto;
text-align: justify;
}

If the language installed in your Windows is the same as the language declared in the index.html, then you get to see the formatting. However, if you decide to put some French text as a sample and change the language to <html lang="fr"> then the hyphenation is gone.

tl;dr Edge provides fancy CSS hyphens only for one language (i.e. the one you use in Windows)

Attachments

1 attachment

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Ibrahim O.”

    Changed Assigned To to “Rick J.”

    Changed Assigned To to “Bogdan B.”

    Changed Steps to Reproduce

  • As the author of this particular piece of feedback, I got to ask - any progress regarding this issue?

  • This problem applies for IE11 too.

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

Sign in