Closed Bug 1827 Opened 26 years ago Closed 26 years ago

Frame size not found

Categories

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

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

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: michael.j.lowe, Assigned: karnaze)

References

(
URL
)

Details

In this page, the program does not correctly pick up the frame column sizes from this tag: <FRAMESET COLS="150,* " FRAMESPACING=0 FRAMEBORDER="NO" BORDER=0>
Status: NEW → ASSIGNED
Rick, should this be handled by the parser?
Rick, should this be handled by the parser?
Assignee: karnaze → rickg
Status: ASSIGNED → NEW
Component: HTMLFrames → Parser
Status: NEW → ASSIGNED
Assignee: rickg → karnaze
Status: ASSIGNED → NEW
This parses correctly. The tag cited has a COLS attribute whose value is "150,* " (note the space between the asterisk and the close quote. The frame system must deal with this, not the parser.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
This is now fixed, but Raptor and Nav 4 still both don't handle other cases where whitespace is inserted in questionable places (e.g rows=" 100, * ")
Status: RESOLVED → REOPENED
Just pulled and built nglayout, but the cited URL above still exhibits the same problem.
Changed was backed out by cltbld%netscape.com since it was applied against a closed tree. Change needs to be reapplied.
Setting all current Open/Normal to M4.
Yes, my change was backed out yesterday by the build team. I will put it back in today.
Status: REOPENED → RESOLVED
Closed: 26 years ago → 26 years ago
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.