1363235 - texhtml UTF-8 chars do not display until 'Inspect Element' used

Status: RESOLVED INCOMPLETE

(Core :: Layout: Text and Fonts, defect, P3)

Description

[JVD]

Attachment: eq.png

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0
Build ID: 20170418074700

Steps to reproduce:

At https://en.wikipedia.org/wiki/Vector_space ,
just above section 'Basis And Dimension', there is this in the HTML :
<quote><pre>
<![CDATA[
<span class="texhtml"><i>f</i>′′(<i>x</i>) + 2<i>f</i>′(<i>x</i>) + <i>f</i>(<i>x</i>) = 0
</span>
]]>
</pre></quote
ie. there are the embedded UTF8 sequences :
    \\xE2\\x80\\xB2
(backslashes doubled to ensure it displays) .

When displayed in  Firefox Developer Edition 54.a2 for Linux  , 
these UTF-8 sequences display like broken / missing glyphs
(as shown in attached screen dump), even after page reload,
UNTIL I select the element (highlight its text) and press 
right-mouse , so that the menu popup appears and I 
choose 'Inspect Element' . Then, and only then, when I move 
the cursor to the element in the Inspector, do the UTF-8
glyphs actually display in the browser .


Actual results:

UTF-8 glyphs in texhtml sections do not appear in browser until
'Inspect Element' is selected for the element containing them, 
and the cursor in the Inspector is moved to the element. 


Expected results:

UTF-8 glyphs in texhtml elements should not need use of Inspect Element to display.

Comment 2

[Jonathan Kew [:jfkthame]]

The characters there are the Unicode character PRIME (U+2032). I tried viewing the page with both Developer Edition and Firefox Nightly on my Linux system, but did not see this problem; the prime characters looked as expected (without using the Inspector).

Are you still seeing this with a current version of Firefox, or has it been resolved somehow in the meantime?

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

A needinfo is requested from the reporter, however, the reporter is inactive on Bugzilla. Closing the bug as incomplete.

For more information, please visit BugBot documentation.