Closed
Bug 99652
Opened 23 years ago
Closed 21 years ago
parsing invalid frameset values for cols and rows
Categories
(Core :: Layout: Images, Video, and HTML Frames, defect)
Tracking
()
RESOLVED
WORKSFORME
mozilla1.0.1
People
(Reporter: johan, Assigned: john)
References
()
Details
Attachments
(2 files)
1.96 KB,
patch
|
Details | Diff | Splinter Review | |
122 bytes,
text/html
|
Details |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010802 BuildID: 2001090319 Reproducible: Always Steps to Reproduce: 1.just visit the site 2. 3. this site was built with Dreamweaver
Comment 1•23 years ago
|
||
The problem is the following line: <frameset cols="no" rows="74,*" frameborder="0" border="0" framespacing="0"> cols="no" is an invalid value... but we seem to be parsing it as a number and trying to create cols.. ignoring the rows="74,*" Over to parser
Assignee: asa → harishd
Status: UNCONFIRMED → NEW
Component: Browser-General → Parser
Ever confirmed: true
QA Contact: doronr → bsharma
Comment 2•23 years ago
|
||
I can't think of an appropriate Summary, but I'm changing it to something a little bit clearer :) Old Summary: "caan't se anything at this website" New Summary: "parsing invalid frameset values for cols and rows" Is this an invalid bug? (I assume that because it was just assigned, that it truly is a problem.. but I would have personally marked it invalid due to wrong code/syntax)
Summary: caan't se anything at this website → parsing invalid frameset values for cols and rows
Parser does not handle attribute values. It just consumes values and hands it over to layout. Reassigning to rod.
Assignee: harishd → rods
Component: Parser → HTMLFrames
Comment 5•23 years ago
|
||
This fix will make us default to "100%" if we iterate over a value we can't match in any other way. This makes the testcase work fine. Reviews?
sorry but I don't like the patch, it gives illegal values a maximum weight and will create new problems with cols= 200, no or any other strange syntax. I think we should more follow the logic of NS_CONTENT_ATTR_NOT_THERE and omitt the cols(rows) where we can't parse the value
Updated•23 years ago
|
Target Milestone: --- → mozilla1.0.1
Comment 7•23 years ago
|
||
Bulk re-assigning all of Eric's HTMLFrame bugs to John.
Assignee: eric → jkeiser
Comment 8•21 years ago
|
||
*** Bug 220033 has been marked as a duplicate of this bug. ***
Updated•21 years ago
|
Target Milestone: Future → mozilla1.0.1
Comment 10•21 years ago
|
||
Actually, I think hwaara's patch may have been the right thing. Consider the following <frameset> decls, which should all be equivalent (the first three per spec, the last one by common sense): <frameset cols="*" rows="50%, 50%"> <frameset rows="50%, 50%"> <frameset cols="100%" rows="50%, 50%"> <frameset cols="garbage" rows="50%, 50%"> All that said, the testcase (about to be attached) worksforme, so marking the bug accordingly.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Comment 11•21 years ago
|
||
Updated•6 years ago
|
Product: Core → Core Graveyard
Updated•6 years ago
|
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
You need to log in
before you can comment on or make changes to this bug.
Description
•