If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Special character symbol not being displayed correctly.

VERIFIED FIXED in M4

Status

()

Core
Layout
P2
normal
VERIFIED FIXED
19 years ago
6 years ago

People

(Reporter: Chris Petersen, Assigned: michaelp)

Tracking

Trunk
x86
Windows 95
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

19 years ago
Build: 11/23 Version: xpviewer.exe and viewer.exe  Platform: Window 95, 98.

1) Launch xpviewer.exe or viewer.exe.
2) Go to either aol, cnet, or geocities web site. These pages contain the special
character symbol "&#149".
3) This symbol should be displayed as solid bullets.
4) The symbol is displayed as double quotes.

Comment 1

19 years ago
Kipp -- I just checked, and this works fine on my NT box.

Updated

19 years ago
Summary: Special character symbol not being displayed correctly. → ss:Special character symbol not being displayed correctly.

Comment 2

19 years ago
Putting on ss: radar, but would his really be an ss:?  I don't think so.  Rick?

Updated

19 years ago
Status: NEW → ASSIGNED

Comment 3

19 years ago
I don't think this should be a "stop ship".

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED

Comment 4

19 years ago
rickg thinks this is Fixed.  Moving to Resolved/Fixed for verification by QA.
If not fixed, reopen and take off ss: list.
(Reporter)

Updated

19 years ago
Status: RESOLVED → REOPENED
(Reporter)

Comment 5

19 years ago
Checked with released build: 11/24

This problem is doesn't happen under Windows NT, but still happens under Win 95
and 98.

Updated

19 years ago
Assignee: kipp → michaelp
Status: REOPENED → NEW

Comment 6

19 years ago
Michael: can you look into this. I've uploaded a page onto klink,
http://klink/ascii.html, that contains &# entities for each and every character.
If you could compare the display on a windows 95/98 box vs. NT and look into why
we don't render certain characters on 95/95, it would be great.

Note: don't bother looking at that page in navigator; it can't render it.

Comment 7

19 years ago
need to mark this bug RESOLVED-FIXED or take out the FIXED resolution
and leave it as NEW.
(Reporter)

Updated

19 years ago
Resolution: FIXED → ---

Updated

19 years ago
Summary: ss:Special character symbol not being displayed correctly. → Special character symbol not being displayed correctly.

Comment 8

19 years ago
Taking off ss: list per bug mtg today.

Comment 9

19 years ago
Using 99/01/25 build --
HTML 4.0 specified numeric character references above #255 don't work, but their
corisponding character entity references do. (i.e. ™ [™] as
aposed to ™ [™]) I will upload a page to demonstrate this soon.
(firewall at work seems to kill ftp transfer)

Comment 10

19 years ago
as promised, here is the test page http://www.improv.ca/mozilla/entity_test.html

and, as you will see, the behaviour is a little weirder then I had originally
thought. There is a link on that page to my original test page, that led me to
the previous comment.

Comment 11

19 years ago
Setting all current Open/Normal to M4.

Updated

19 years ago
QA Contact: 3849

Comment 12

19 years ago
I reviewed the entities listing and the trademark symbol does appear in the most
recent build, by the character entity and code value. There are still numerous
other characters that do not. Specifically in the Greek, Math, Misc and General
Punctuation segments. Also, all other Leterlike characters are not recognized.
But, since this bug was originally written for charcter #149, and it does not
render as a bullet, but as a double quote.

Updated

19 years ago
Status: NEW → RESOLVED
Last Resolved: 19 years ago19 years ago
Resolution: --- → FIXED

Updated

19 years ago
Status: RESOLVED → VERIFIED

Comment 13

19 years ago
using 3/4 build, on win95, the entity #149 renders as a bullet. Marking fixed
and verified

Updated

11 years ago
You need to log in before you can comment on or make changes to this bug.