Closed Bug 243435 Opened 21 years ago Closed 21 years ago

View Selection Source shouldn't render HTML Character Codes.

Categories

(Core Graveyard :: View Source, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 230710

People

(Reporter: mozillabugs, Assigned: doronr)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8 If the HTML source contains a character code (such as & or "), doing a View Selection Source on the character shows the rendered character. This is contrary to the behavior of the regular old View Source. Reproducible: Always Steps to Reproduce: 1. View Selection Source on a character that is encoded in the source, such as & Actual Results: View selection source displays the & character Expected Results: View selection source should display the proper character code (&) This happens in both Firefox 0.8 and 1.7b (20040421). As a developer, I just wasted an hour trying to figure out why my convert_quotes() PHP function was not properly converting " to " ... turns out my function was working all along, the bug was with how Mozilla displays character codes with View Selection Source! View Selection Source behavior should be consistant with the regular old View Source behavior. I will attach a test case.
I can't seem to create a simple testcase that exhibits this bug, but I've added a testcase URL, which validates as XHTML 1.0 Transitional: http://www.tumyeto.com/product.php?catproductid=1885 Select one of the quotes and View Selection Source, you will see the HTML character codes rendered (the " character is displayed). Now do a regular old View Page Source and you will see them displayed properly as their HTML character codes (")
Once it's just a character in the DOM, there's no way to know it came from an entity reference. *** This bug has been marked as a duplicate of 230710 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
> I just wasted an hour Reporter, was that in Firefox? Wasting so much time chasing inexisting issues can be frustrating. Do you think using 'DOM Source' in the title would have helped? CC: yourself to bug 236465 if you are interested.
Product: Browser → Seamonkey
Product: SeaMonkey → Core Graveyard
You need to log in before you can comment on or make changes to this bug.