Closed
Bug 33857
Opened 24 years ago
Closed 24 years ago
Frameset splitter movement is broken/sluggish and does not stay where you drop it
Categories
(Core :: Layout: Images, Video, and HTML Frames, defect, P3)
Tracking
()
People
(Reporter: billw, Assigned: pollmann)
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; N; NT4.0; en-US) Mozilla/m13 BuildID: 2000022820 When a window split is moved on a page with frames, the splitter moves to a position OTHER than where it was specified to move to (beyond, ie larger than), and the extra section scrolls very strangely. The scroll bars disappear, so one must use the mouse to scroll up and down. Reproducible: Always Steps to Reproduce: 1.Create a javadoc set of documentation 2.Open index.html 3.Move splitter Actual Results: Splitter moves to different position. Right-hand window behaves VERY strangely. Scroll bar disappears. Expected Results: Splitter should move to dropped position. Splitter should move smoothly. Right-hand window should be re-sized properly. Scroll bar should be redrawn. I would provide an example, but mozilla crashes on www.javasoft.com every time I try to go there.
Assignee | ||
Comment 1•24 years ago
|
||
I think I've seen this one before, I'll look for the duplicate...
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Table splitter movement is broken/sluggish and does not stay where you drop it → Frameset splitter movement is broken/sluggish and does not stay where you drop it
Assignee | ||
Comment 2•24 years ago
|
||
Found it, bug 12002. I recently fixed the problem where nested framesets don't calculate their resizing offsets correctly. This should fix any problems with "not staying where you release it". *** This bug has been marked as a duplicate of 12002 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
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
•