Closed Bug 23857 Opened 26 years ago Closed 25 years ago

Sidebar fills entire screen on splitter click

Categories

(Core :: XUL, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: slamm, Assigned: eric)

References

Details

(Keywords: platform-parity)

Attachments

(1 file)

On Linux-only, sometimes when you click on the grippy to close the sidebar, the sidebar fills the entire screen (the splitter goes off the window). This is not all that easy to reproduce, on the sidebar, but I made a simpler testcase where it happen more readily (see attachment). I originally suspected an interaction between iframes and boxes, but my testcase does not use any iframes. If fact, the only box is from the <window> tag.
Severity: normal → critical
Marking critical.
Status: NEW → ASSIGNED
Target Milestone: M14
*** Bug 22096 has been marked as a duplicate of this bug. ***
*** Bug 17350 has been marked as a duplicate of this bug. ***
Target Milestone: M14 → M15
Blocks: 24700
Keywords: pp
This causes the entire browser window to go blank. Just about as bad as a crash. Workaround is to open a new window (if you know where to click for the menu since is doesn't show anymore).
Keywords: beta1
Whiteboard: [pdt+]
Blocks: 25824
Blocks: 26981
Summary: [PP] Sidebar fills entire screen on splitter click → Sidebar fills entire screen on splitter click
Can't seem to repoduce this. Does this happen anymore with the current build? If not can you close it out?
Assignee: evaughan → slamm
Status: ASSIGNED → NEW
No longer blocks: 25824
shrir, can you reproduce with latest build? Any one still seeing this? Can we mark WorksForMe.?
QA Contact: paulmac → shrir
Whiteboard: [pdt+] → [pdt+] Trying to reproduce 02/23
Still happens on Linux. Back to evaughan.
Assignee: slamm → evaughan
Whiteboard: [pdt+] Trying to reproduce 02/23 → [pdt+] Still happens on Linux 2/29
Ok I have reproduced this. It is linix only. Have no idea why. But I'm looking at it.
Status: NEW → ASSIGNED
Whiteboard: [pdt+] Still happens on Linux 2/29 → [pdt+] 3/3/00 working on this one.
We need a status update on this. It is also critical to understand how easy this is to reproduce, how obvious the workaround (if any) when it hits is, etc. Thanks, Jim
removing PDT+ for reconsideration. This is an obscure bug that few people are seeing, even when they try to reproduce it. It should not be marked critical severity since there is no crash, data loss or severe leak. There is even a workaround. Who would really hold a first Preview Release for this?
Whiteboard: [pdt+] 3/3/00 working on this one. → 3/3/00 working on this one.
Putting on PDT- radar for beta1.
Whiteboard: 3/3/00 working on this one. → [PDT-]3/3/00 working on this one.
Mass-moving most M15 bugs to M16
Target Milestone: M15 → M16
downgrading severity to normal.
Severity: critical → normal
nominating for beta2
Keywords: beta1nsbeta2
fixed
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Whiteboard: [PDT-]3/3/00 working on this one.
verified (2000060208)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: