Add &nnbsp; entity for U+202F
Categories
(Core :: DOM: HTML Parser, enhancement)
Tracking
()
People
(Reporter: ygoe, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
This is a feature request or more an idea of an extension to the HTML standard. I've already opened the issue here:
https://github.com/whatwg/html/issues/5121
Not sure if this bug tracker is a good place to ask for this. But the other issue is labelled as "needs implementer interest" so I thought it might help to make those implementers aware of the issue.
Should I repeat the complete issue text here as well? Please advise.
|
||
Comment 1•5 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
|
||
Updated•5 years ago
|
|
||
Comment 2•5 years ago
|
||
We don't use Bugzilla for non-standard features generally. We'd probably pick this up if other browsers did it and went through the trouble of writing tests and such, but I'm not convinced it's worth the effort.
|
Reporter | |
Comment 3•5 years ago
|
||
Just to be sure I understand this correctly, changes to the HTML standard will only be made when browsers show interest, but Mozilla doesn't want to be the one that shows this interest? I'll also ask the Chrome people but then I have no more options for innovation since there are no other browsers.
I clearly have no idea of what it takes to implement this; I'd have thought it's a few list entries here and there and a few test cases for them to add a new and currently undefined HTML entity. Since it's only about converting HTML into Unicode, and that Unicode character can already be written directly, it shouldn't have too many consequences.
Don't get me wrong, I'm by no means requesting any certain time schedule. But this addition would be very helpful in the end to achieve good-looking (and typographically correct – for other languages than English) results with yet unachieved maintainability.
Description
•