953014 - Entity decoding has changed some, but not all characters.

Status: RESOLVED INVALID

(Firefox :: Untriaged, defect)

Description

[Bryan Price]

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20131223030203

Steps to reproduce:

Bring up a page that displays HTML entities like:
http://www.bryanlprice.com/specials.html
http://www.fileformat.info/info/unicode/category/So/list.htm




Actual results:

Then entities for copyright (©, ©), registered (®, ®), trademark (&trade, ™), and horizontal ellipsis (…, …) no longer show as one character, they are now broken down into separate characters.  (c) for ©, (r) for ®, (tm) ™, and ... for ….  Interestingly enough, ℗, ℗ for sound recording copyright was NOT changed.


Expected results:

I should get a correctly encoded character instead of a stream of characters to represent those characters.  I should get © in my display, not (c).

Comment 1

[iamjayakumars]

Hi Bryan, Could you attach the screenshot, because i'm not facing this issue in MAC.

So we make sure it happens only with windows systems or your system issue.

System Info

Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20131223030203 CSet: c0f85061c7d3

Comment 2

[Tony Mechelynck [:tonymec]]

This is the kind of issue which "might" belong in some component of the Core product, in which case it would also affect Thunderbird (when reading HTML mail) and SeaMonkey (browser and HTML mailer).

I cannot test it because I am using SeaMonkey on Linux, where the most recent trunk builds are version 2.24a1 (Gecko 27.0a1). There are SeaMonkey 2.26a1 (Gecko 29.0a1) nightlies for Windows and Mac, however. Phoenix, are you on Windows? If you aren't, do you know who is? If you are, can you test if this bug affects SeaMonkey 2.26a1?

OTOH, Bryan, if this issue is caused by some misbehaving extension (there are so many available extensions nowadays, you never now _how_ they can misbehave), it should disappear in Safe Mode (Help → Restart with Add-ons Disabled) or in a clean profile (see http://kb.mozillazine.org/Profile_Manager#Creating_a_new_profile ).

Comment 3

[Tony Mechelynck [:tonymec]]

Oh, and now I think of it, Wayne, you should be able to write an HTML email message with the problematic entities mentioned under "Actual results" in comment #0 (entities, NOT their UTF-8 equivalents), to see if the latest Daily displays them as one character each (good) or several characters (bad).

Comment 4

[Masatoshi Kimura [:emk]]

Works for me on Windows XP.

Comment 5

[Bryan Price]

And, as I check things out more, I have finally figured out that it is a new extension that has done me in.  Sorry people. :(

Comment 6

[Tony Mechelynck [:tonymec]]

(In reply to Bryan Price from comment #5)
> And, as I check things out more, I have finally figured out that it is a new
> extension that has done me in.  Sorry people. :(

Happy you found out. Next time I guess you'll check a little more before opening a bug. But the worst of all would be letting a real bug go unreported, because an unreported bug cannot be fixed.

Merry christmas!

Comment 7

[Tony Mechelynck [:tonymec]]

emk: I see you removed the "regression" and "regressionwindow-wanted" keywords. Just for my own edification (as a triager): what difference do they make on a bug which was already RESOLVED INVALID?