Closed Bug 3092 Opened 26 years ago Closed 26 years ago

www.projo.com: ((SCRIPT && STYLE) in TABLE) => duplicate rows

Categories

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

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

Tracking

()

Status:
VERIFIED DUPLICATE of bug 2701

People

(Reporter: 3jrgm, Assigned: karnaze)

References

(
URL
)

Details

This HTML (below) produces the following. (Reduced from www.projo.com)

             +-------+-------+
             | (1,1) | (1,2) |      <-- duplicate row
             +-------+-------+
             | (1,1) | (1,2) |
             +-------+-------+
             | (2,1) | (2,2) |
             +-------+-------+

1) Removing *either* the <SCRIPT></SCRIPT> or the <STYLE></STYLE> lays
out the table correctly. (And, yes, the <STYLE> should definitely not
be there, but it's in the original HTML in that location)

2) Reversing the positions of SCRIPT and STYLE eliminates the error
(i.e., put STYLE in the first row and SCRIPT in the second row).

(Tested on Feb06 Win95 non-debug build). [Note: this is not the same
bug as the old one (#1224) which is FIXED.]

 ==============================
<html><head></head><body>
<table border="1" width="400">
  <tr>
    <td>
       (1,1)
    </td>
    <td>
       (1,2)
      <SCRIPT></SCRIPT>
    </td>
  </tr>
  <tr>
    <td>
       (2,1)
      <STYLE></STYLE>
    </td>
    <td>
       (2,2)
    </td>
  </tr>
</table>
</body></html>
Assignee: rickg → karnaze
Chris -- This is not a parser bug as stated. If you dump the content model, it
appears correctly.
Hey, John ---

Killer decomposition. You rock. What you're describing sounds like the bug that
3054 describes (view source on the http://www.ea.com/static_main.html frame).

Do you think it's a duplicate?
As it turns out, no, not a duplicate. #3054 appears to be a problem with
document.write, and I put a test case to show the problem over at #3054.
.. John
<Thanks for checking. We are not worthy. ;->
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
Not worthy?

*** This bug has been marked as a duplicate of 2701 ***
Status: RESOLVED → VERIFIED
Verified Dup of Bug 2701
You need to log in before you can comment on or make changes to this bug.