Closed Bug 863 Opened 26 years ago Closed 26 years ago

we dont' support the hex notation for numeric character references

Categories

(Core :: DOM: HTML Parser, defect, P2)

Product:
Core
Component:
DOM: HTML Parser
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: kipp, Assigned: rickg)

References

(
URL
)

Details

and we should
Assignee: rickg → kipp
Well, upon closer inspection, we consume hex entities (such as &#x4cE) just fine. What you get out is (in this case): x4cE. Note that the leading &# has been stripped (as we discussed a long time ago). Do you want me to prepend the &# characters?
Assignee: kipp → rickg
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
I changed the parsernode and nsString to correctly deal with hex entities. The string ToInteger() code now accepts a radix argument.
QA Contact: 4082
Kipp can you please mark this verified or let me know it is cool for me to do so? Thanks. GL
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: --- → FIXED
This is fixed. Please retry. I used the test case: <html> <body> entity: &#xA9;<BR> </body> </html>
Status: RESOLVED → VERIFIED
Verified as fixed; copyright properly shown per last test case.
You need to log in before you can comment on or make changes to this bug.