Closed Bug 1123632 Opened 9 years ago Closed 8 years ago

Shumway doesn't parse XML correctly

Categories

(Firefox Graveyard :: Shumway, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: tech4pwd, Unassigned)

References

Details

Component: Untriaged → Shumway
Thanks for reporting. There's an issue with our XML parser here. It chokes on the following, well-formed input:

<settings>  <General_Properties>    <position value="bottom"/>    <hide value="alpha"/>    <slideDirection value="leftright"/>    <time value="1"/>    <motion value="Cubic"/>    <ease value="easeOut"/>    <useButton value="false"/>    <arrow value="assets/redarrow.png"/>    <margin value="0"/>    <path value="DockMenuFX"/>    <showAbout value="true"/>  </General_Properties></settings>

For some reason it parses this into two top-level nodes, one for <settings>, which contains the entire correctly parsed content, and an empty one that shouldn't be there at all.
Is that just a Shumway problem or a global Firefox/Gecko issue?
(In reply to Paul [pwd] from comment #2)
> Is that just a Shumway problem or a global Firefox/Gecko issue?

Just Shumway, it has nothing to do with the rest of Firefox at all.
(In reply to Till Schneidereit [:till] from comment #3)
> (In reply to Paul [pwd] from comment #2)
> > Is that just a Shumway problem or a global Firefox/Gecko issue?
> 
> Just Shumway, it has nothing to do with the rest of Firefox at all.

I only just enabled Shumway the other day and am yet to grasp all the details like how deeply it's integrated into Firefox. It's all very new and very exciting to me. Thanks for taking the time to answer my question.
Blocks: shumway-1.0
Summary: FlashXML examples with embedded images not working → Shumway doesn't parse XML correctly
Blocks: shumway
Blocks: shumway-m5
No longer blocks: shumway-1.0, shumway
Status: UNCONFIRMED → NEW
Ever confirmed: true
Product: Firefox → Firefox Graveyard
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.