Closed
Bug 25382
Opened 26 years ago
Closed 26 years ago
Table displaying input
Categories
(Core :: Layout: Tables, defect, P3)
Tracking
()
VERIFIED
FIXED
People
(Reporter: trentjarvi, Assigned: harishd)
References
()
Details
(Keywords: helpwanted)
Attachments
(1 file)
|
118 bytes,
text/html
|
Details |
I noticed that the stock quote page on cnbc was different between M13 and
netscape 4.7 on linux. M13 was not displaying the table that has the input
for a new stock quote price.
I tried to chop out as much html as possible while still reproducing the
difference and ended up with the following:
<html><body><form>
<img src=x.gif>
<table><tr><input></tr></table>
</form></body</html>
It does not matter if x.gif is there or not. The difference is still
observable. adding <td> tags resolves the issue but I'd think mozilla would
not want to drop 1/3 of a page because someone forgot a <td> tag and checked it
with a different browser.
Comment 1•26 years ago
|
||
The relevant field on the original page displays fine for me in Win95 M13.
However, the test case (now attached) does do different things in M13 and
Navigator 4.7. This could be, though, because the HTML in the test case is
almost certainly illegal, so Moz could be perfectly within its rights to barf on
it.
I'm also not convinced by the reporter's dodgy reasoning on broken HTML ;-)
IMO, if
- the test case turns out to be illegal HTML
- this can't be reproduced on Linux
we should close this.
Help Wanted: HTML Guru to check the HTML of the test case (quoted above, and
attached) and Linux bod to check the original page in M13 or later.
Gerv
Whiteboard: HELP WANTED
Comment 2•26 years ago
|
||
Comment 3•26 years ago
|
||
Harish, the parser is not creating a <tr> for the <input> inside the <tr>.
Assignee: karnaze → harishd
Updated•26 years ago
|
Keywords: helpwanted
Whiteboard: HELP WANTED
The reason was, INPUT was considered legal, anywhere, in the TABLE and therefore
did not get moved out of the TABLE. This problem is FIXED.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•