Closed Bug 1323 Opened 26 years ago Closed 25 years ago

We aren't "compounding" frameset scrollbars

Categories

(Core :: Layout: Images, Video, and HTML Frames, defect, P1)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: angus, Assigned: karnaze)

References

()

Details

(Whiteboard: handing back (1223 fixed))

This URL has a frameset like this: --------- |___ A____| | | | |B | | | | C | | | | ----------- Frame A should not have any scrollbars (has scrolling=no attribute) Frame B should have auto scrolling Frame C should also have auto scrolling. Frame C is the right most frame. Becuase Frame C is along the right, it's scrollbar should be to the immediate left of the Viewer's window border, where a normal scrollbar would appear. Instead, the frameset document is getting a scrollbar all its own, and then to the left of *that* scrollbar is another scrollbar for frame C! You might need to resize (enlargen) the viewer window to see this bug. I'm using 11-9-98 Optimized bits.
Status: NEW → ASSIGNED
Assignee: karnaze → vidur
Severity: normal → critical
Status: ASSIGNED → NEW
Priority: P2 → P1
I can't fix the bug because it is crashing in javascript. Please reassign it back to me when the crash is fixed. I've cc'ed Rick G since the parser is in the stack as well.
Assignee: vidur → fur
The script problem is because of bug 1223, assigned to fur@netscape.com. Since I don't want to lose the original bug, I'm not resolving it as a DUP. I am, however, assigning it to Scott so that he can return it to Chris Karnaze once the bug is fixed.
Setting all current Open Critical and Major to M3
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Assignee: fur → mccabe
Same as #1223
Target Milestone: M3 → M4
lets try and get this for M4.
QA Contact: 4082 → 4110
re-assigning chrisd D as qa_contact.
QA Contact: 4110 → 3849
Status: NEW → ASSIGNED
Setting this bug and friends to m5. I hope to get to it soon. (But I'm guessing it reflects a subtle change to the semantics of javascript variable lookup, so I don't want to make that change without a full run of the javascript testsuite.)
Whoops, actually changing the setting...
These bugs seem to be different aspects of 1223. Shaver has graciously taken 1223; reassigning these to him. (thanks, Mike)
Whiteboard: need status update
Target Milestone: M5 → M6
moving to m6
Status: NEW → ASSIGNED
Assignee: shaver → karnaze
Status: ASSIGNED → NEW
Whiteboard: need status update → handing back (1223 fixed)
1223 is fixed, so this is back to Chris.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Fixed with recent checkins.
Status: RESOLVED → VERIFIED
tested and verified the fix.
Product: Core → Core Graveyard
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.