Chrome breaks layout if system language is Chinese
See original GitHub issueDescription
Only chrome meet the bug,safari and firefox are correct.
the case include my “mkdocs serve” and your “https://squidfunk.github.io/mkdocs-material/”
this is chrome:

this is firefox:

Package versions
- Python:
2.7.10 - MkDocs:
1.0.4 - Material:
3.0.6
Project configuration
site_name: My Docs
theme:
name: material
System information
- OS: macos 10.13.4
- Browser: chrome
Issue Analytics
- State:
- Created 5 years ago
- Comments:39 (22 by maintainers)
Top Results From Across the Web
42984 - Chrome breaks Windows 7's display of Unicode
The Chrome breaks the display of unicode in Windows 7 Utimate (x64). ... Set Chinese/Japanese/Korean as the language of application. Chrome ...
Read more >Change Chrome languages & translate webpages - Computer
On your computer, open Chrome. · At the top right, click More More and then · At the bottom, click Advanced. · Click...
Read more >Typing Chinese Characters on Chromebook - Google Sites
1) If the language you want to use isn't shown in the list to the left, click Add. 2) Select “Chinese (Traditional) 中文(繁體)”,...
Read more >Japanese fonts not rendered correctly - Han Unification
When I set the language to Japanese, it renders it as if it is Chinese. This is a common problem that is caused...
Read more >LayoutNG - Chrome Developers
A new layout engine for Chromium. ... (See Chromium bug #6122.) A grapheme is the smallest unit of a language's writing system.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I don’t see any mistakes in https://github.com/squidfunk/mkdocs-material/commit/2007484306d00906f4ab9e1981d35d4d7eb0b6ab
The bug is fixed on my Chrome. Thannk you!