I recently discovered [this historical document](https://www.w3.org/2001/06/utf-8-test/UTF-8-demo.html), which purports to act as a test of UTF-8 encoding for whatever application displays it.

When I paste it into my terminal (iterm2), it loads the box drawings at the end beautifully (except for a couple at bottom right):

[![correctly rendered unicode box drawings](https://i.stack.imgur.com/jl74e.png)](https://i.stack.imgur.com/jl74e.png)

But in both Chrome and Firefox, they are crooked and clearly wrong:

[![incorrectly rendered unicode box drawings](https://i.stack.imgur.com/xoqp7.png)](https://i.stack.imgur.com/xoqp7.png)

It seems the difference has to do with the width of the rendered character: for example "╲" displays in my terminal as wide as other characters such as "a", but in the browser it displays wider.

Is this a deliberate choice, and if so what inspired it? If not, where is the right place to file a bug?

**EDIT**

Thanks to [Tom Blodget's answer](https://stackoverflow.com/a/54726628/3229874), I am now aware that fonts are an important consideration. I'll clarify:

In my screenshots above, Firefox and Chrome are using Courier as the monospace font, while the terminal is using Monaco. In both contexts, the font seems to apply as much to the box-drawing characters as to the ASCII ones: when I change the font, the appearance of the drawings changes as well as that of the surrounding text.

When I switch the terminal to either Courier or Courier New, it shows the box drawings equally well -- in some ways better!

When I switch either browser to Monaco, it still shows the box drawings wrong, again from characters apparently displaying at a wider-than-monospace width.

So it still seems like the browsers are doing something wrong.