Closed Bug 5790 Opened 26 years ago Closed 26 years ago

XML parsing is incorrect when a table is root element

Categories

(Core :: XML, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: karnaze, Assigned: nisheeth_mozilla)

Details

This bug is a spin off of bug 5190 which is now fixed. The following example from that bug only has content for the 1st row. There appears to be a bug in the xml parser or content sink. You can verify this by dumping content in the Viewer. --------- foo.xml -------------- <?xml version="1.0"?> <?xml-stylesheet href="keytable.css" type="text/css"?> <!DOCTYPE keyboard [ <!ELEMENT keyboard (row+)> <!ATTLIST keyboard type CDATA #IMPLIED> <!ELEMENT row (key+)> <!ELEMENT key ( (upper, lower) | special )> <!ELEMENT upper (#PCDATA)> <!ELEMENT lower (#PCDATA)> <!ELEMENT special (#PCDATA)> ]> <keyboard type="dvorak"> <row> <key><upper>~</upper><lower>`</lower></key> <key><upper>!</upper><lower>1</lower></key> <key><upper>@</upper><lower>2</lower></key> <key><upper>#</upper><lower>3</lower></key> <key><upper>$</upper><lower>4</lower></key> <key><upper>%</upper><lower>5</lower></key> <key><upper>^</upper><lower>6</lower></key> <key><upper>&amp;</upper><lower>7</lower></key> <key><upper>*</upper><lower>8</lower></key> <key><upper>(</upper><lower>9</lower></key> <key><upper>)</upper><lower>0</lower></key> <key><upper>£</upper><lower>µ</lower></key> <key><upper>+</upper><lower>=</lower></key> </row> <row> <key><upper>&quot;</upper><lower>'</lower></key> <key><upper>&lt;</upper><lower>,</lower></key> <key><upper>&gt;</upper><lower>.</lower></key> <key><single>P</single></key> <key><single>Y</single></key> <key><single>F</single></key> <key><single>G</single></key> <key><single>C</single></key> <key><single>R</single></key> <key><single>L</single></key> <key><upper>?</upper><lower>/</lower></key> <key><upper>}</upper><lower>{</lower></key> <key><upper>|</upper><lower>\</lower></key> </row> <row> <key><single>A</single></key> <key><single>O</single></key> <key><single>E</single></key> <key><single>U</single></key> <key><single>I</single></key> <key><single>D</single></key> <key><single>H</single></key> <key><single>T</single></key> <key><single>N</single></key> <key><single>S</single></key> <key><upper>_</upper><lower>-</lower></key> <key><special>SHLK</special></key> <key><special>RET</special></key> </row> <row> <key><special>SHFT</special></key> <key><upper>:</upper><lower>;</lower></key> <key><single>Q</single></key> <key><single>J</single></key> <key><single>K</single></key> <key><single>X</single></key> <key><single>B</single></key> <key><single>M</single></key> <key><single>W</single></key> <key><single>V</single></key> <key><single>Z</single></key> <key><special>DEL</special></key> <key><special>SPC</special></key> </row> </keyboard> ---- keytable.css ---------- keyboard { display: table; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10pt; padding: 10pt; padding-top: 5pt; color: black; background: black; empty-cells: show; table-layout: auto; border-collapse: collapse } row { display: table-row; padding-top: 8px; } key { display: table-cell; cursor:pointer; background: #BBB; padding-left: 3px; padding-right: 3px; padding-bottom: 2px; margin-right: 2px; border: 2px outset #BBB; } upper { display: inline; font-size: 8pt; vertical-align:top; color: #EEE; margin-bottom: auto; margin-top: auto; } lower { display: inline; padding: 2px; font-weight: bold; margin-bottom: auto; margin-top: auto; } special { display: inline; font-weight: bold; margin-bottom: auto; margin-top: auto; } single { display: inline; font-weight: bold; margin-bottom: auto; margin-top: auto; }
Status: NEW → ASSIGNED
Setting target milestone to M7...
Target Milestone: M7
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
The content model is being constructed proprly now. Rickg's latest parser fixes must have fixed this problem. Marking resolved.
Status: RESOLVED → VERIFIED
Using 6/7 Apprunner, file displays correctly. Verifying bug fixed.
You need to log in before you can comment on or make changes to this bug.