Closed Bug 1141401 Opened 9 years ago Closed 8 years ago

Robustness improvements for JSDOMParser

Categories

(Toolkit :: Reader Mode, defect)

Product:
Toolkit
Component:
Reader Mode
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: fabrice, Unassigned)

Details

What's currently not working about JSDOMParser? The page in question renders in reader mode fine - it misses paragraphs, but that's likely readability's fault, not jsdomparser. As it is, this report is incomplete because it lacks the information required to take action on it.

For some background: JSDOMParser requires an XML-compatible DOM string. There is no real reason to relax that requirement (we make sure the thing it gets from firefox is xml-compatible even if the original document wasn't by using an xml-based serializer). For a more robust parser, maybe see jsdom ( https://github.com/tmpvar/jsdom/ ).
Flags: needinfo?(fabrice)
When I filed this bug I was feeding it the raw http response, because I didn't want to go through a parse-then-reserialize-then-reparse chain. I'm not working on that anymore, so feel free to ignore.
Flags: needinfo?(fabrice)
Thanks, going to resolve WFM then.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.