362147 - DOM Inspector #text nodes don't show some characters

Status: RESOLVED INCOMPLETE

(Other Applications :: DOM Inspector, defect)

Description

[Chris Dolan]

The DOM Inspector fails to render some entities within text nodes.  The referenced URL is a trivial web page containing a single "↑" in the body.   Upon clicking this node in the DOM Inspector, nothing appears in the right-hand pane, which usually shows the contents of the text node.

If I change the entity to be "7" (aka "7"), then the inspector renders it properly.  So, it appears that it's a Unicode or font problem instead of a problem with the entity.

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0

Comment 1

[Shawn Wilsher :sdwilsh]

WFM
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.7) Gecko/20060911 Red Hat/1.5.0.7-0.1.el4 Firefox/1.5.0.7 pango-text

I'll check my MacBook which is running 2.0 later this evening.

Comment 2

[Shawn Wilsher :sdwilsh]

Attachment: testcase

Testcase from URL.

Comment 3

[Chris Dolan]

(In reply to comment #2)
> Created an attachment (id=246855) [edit]
> testcase
> 
> Testcase from URL.

Your test case does not reproduce the bug on my machine.  The original URL is reproduceable on two Macs running 10.4 and Firefox 2.0

Comment 4

[Shawn Wilsher :sdwilsh]

(In reply to comment #3)
> Your test case does not reproduce the bug on my machine.  The original URL is
> reproduceable on two Macs running 10.4 and Firefox 2.0

My testcase was just the html file from your url - I attached it because we like to have things attached to bugzilla.

Also, using your url - WFM on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 LNSE/1.0.0 RTSE/1.0.6

Comment 5

[Shawn Wilsher :sdwilsh]

However, confirmed with both url and attached testcase with Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 RTSE/1.1.0.20061116

Comment 6

[Chris Dolan]

(In reply to comment #4)
> (In reply to comment #3)
> > Your test case does not reproduce the bug on my machine.  The original URL is
> > reproduceable on two Macs running 10.4 and Firefox 2.0
> 
> My testcase was just the html file from your url - I attached it because we
> like to have things attached to bugzilla.
> 
> Also, using your url - WFM on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
> rv:1.8.1) Gecko/20061010 Firefox/2.0 LNSE/1.0.0 RTSE/1.0.6

No, your test case has a verbatim Unicode character, mine had an "&#nnnn;" entity.  The HTML source has been altered in your attempt to attach it to this bug.

That said, on my Mac today, I *can* reproduce the bug with your test case.  I could not last night from my Mac at home.  I suspect the difference is that at work I have my default encoding set to UTF-8 while at home I think I have the Firefox default of ISO-8859-1.  Since your copy of the test case lacks encoding info, it's being interpreted differently.

Therefore, I recommend invalidating the current attached testcase and either re-attach it correctly, or just rely on the external URL (which I promise will never change).

Comment 7

[Shawn Wilsher :sdwilsh]

Comment on attachment 246855 [details]
testcase

Apparently you cannot trust File->Save Page As... to save the page.

Comment 8

[Shawn Wilsher :sdwilsh]

This also WFM with Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.9a1) Gecko/20061126 Minefield/3.0a1.

Can we find out for sure that it is just an issue with the default encoding and a document not specifying it perhaps?

Comment 9

[Chris Dolan]

(In reply to comment #8)
> This also WFM with Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.9a1)
> Gecko/20061126 Minefield/3.0a1.
> 
> Can we find out for sure that it is just an issue with the default encoding and
> a document not specifying it perhaps?

My test URL is just ASCII, so encoding should not matter since both UTF-8 and ISO-8859-1 are ASCII supersets, right?  That's why I deliberately used an entity and not a literal character.

Perhaps a file:// test case with a meta content-type with a UTF-8 encoding is the best way to test?  I'm not really sure, and am open to suggestions or more detailed steps to test.

Comment 10

[Firefox Bug Husbandry Bot]

Bulk close. This component is no longer supported or maintained.

https://bugzilla.mozilla.org/show_bug.cgi?id=1499023

Comment 11

[Firefox Bug Husbandry Bot]

Bulk close. This component is no longer supported or maintained.

https://bugzilla.mozilla.org/show_bug.cgi?id=1499023