443882 - Okina (ʻ) displayed incorrectly when emboldened

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Kyle]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0

The Okina character, HTML entity &#699;, seems to turn into another character entirely when emboldened (<b>, <strong>, font-weight:bold;). It looks like the character it turns in to is the standard grave accent (`).

Reproducible: Always

Steps to Reproduce:
1. Open a blank HTML file
2. Put in &#699;<b>&#699;</b>
3. Save file
4. Open file in Mozilla Firefox
5. Observe how the emboldened character is facing a different direction, zoom in or change font size to observe more closely
Actual Results:  
Okina (&#699;) character not the okina (&#699;) character when emboldened.

Expected Results:  
Shown the emboldened version of the okina (&#699;) character.

Comment 1

[Kyle]

Change can only be seen with sans-serif web safe fonts, issue not present when font is Arial Unicode MS or Lucida Sans Unicode. Checked in other browsers, issue not present in Safari or Internet Explorer 6 or 7.

Comment 2

[Kyle]

Attachment: Shows okina character in various browsers and fonts

Comment 3

[Kyle]

Attachment: HTML test of okina character in various fonts

Comment 4

[Tyler Downer [He/Him]]

This is a mass search for bugs that are in the Firefox General component, are
UNCO, and have not been changed for 800 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10, create a fresh profile,
http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you
still see the bug, please update this bug. If the issue is gone, please set the
resolution to RESOLVED > WORKSFORME.

Comment 5

[Tyler Downer [He/Him]]

No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.