Skip to content
This repository was archived by the owner on Apr 17, 2019. It is now read-only.

Switching unicode markers to bdi tags to fix MS browsers showing box characters in text.#116

Open
poscar wants to merge 1 commit into
l20n:masterfrom
poscar:ms_browsers_bdi_fix
Open

Switching unicode markers to bdi tags to fix MS browsers showing box characters in text.#116
poscar wants to merge 1 commit into
l20n:masterfrom
poscar:ms_browsers_bdi_fix

Conversation

@poscar

@poscar poscar commented Mar 23, 2016

Copy link
Copy Markdown

The FSI and PDI characters are displayed as square boxes in Microsoft browsers (see attached screenshot). This pull request fixes that issue by using bdi tags instead.

screen-shot-2016-03-22-at-8 05 49-pm

@Pike

Pike commented Mar 23, 2016

Copy link
Copy Markdown
Contributor

Sadly https://connect.microsoft.com/IE/Feedback/Details/2457310 only has the stock @MicrosoftEdge response.

@poscar

poscar commented Apr 21, 2016

Copy link
Copy Markdown
Author

@stasm Could we merge this one as well?

@zbraniecki

Copy link
Copy Markdown
Member

Ok, so Microsoft is investigating - https://developer.microsoft.com/microsoft-edge/platform/issues/6831905/. I can reproduce this bug in Virtualbox. I'm not sure if it's a virtualbox only or does it also happen in full environment?

I'd like to keep this issue open, but I'm not sure if we should do what the patch suggests. In particular, this would not work in non-HTML environments (Node, JS etc.) so we'd need per-bindings solution.
I'd rather see MS resolve it :)

@poscar

poscar commented May 7, 2016

Copy link
Copy Markdown
Author

@zbraniecki Cool, it'll be great if they fix it. Only issue then will be that older browsers will probably not get the fix.

@zbraniecki

Copy link
Copy Markdown
Member

Only issue then will be that older browsers will probably not get the fix.

Edge is on the train release so I expect them to deliver an update to their users with the fix before we get l20n 4.0 released.

@tomekstach

Copy link
Copy Markdown

@zbraniecki Unfortunately, Edge still has the same problem. Do you have any idea how prepare a workaround for Edge?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants