Closed Bug 32155 Opened 25 years ago Closed 6 months ago

Fix Stack z order

Categories

(Core :: XUL, defect, P5)

Product:
Core
Component:
XUL
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: eric, Unassigned)

References

Details

(Whiteboard: [nsbeta2-][nsbeta3-])

The stack widget was not finished and does not support z order. Stack needs to implement this to support skins. Currently Aqua uses stack extensively. Estimated time: 1 day
targeting
Status: NEW → ASSIGNED
Target Milestone: --- → M15
Summary: [feature] Fix Stack z order → [feature] Fix Stack z order 1 day
moving to m16
Summary: [feature] Fix Stack z order 1 day → [feature] Fix Stack z order
Whiteboard: 1 day
Target Milestone: M15 → M16
*** Bug 33252 has been marked as a duplicate of this bug. ***
adding skins keyword, setting P1. need estimated landing date in status whiteboard, not duration.
Keywords: skins
Priority: P3 → P1
Blocks: 29160
Whiteboard: 1 day → 2 day 4/21/00
Whiteboard: 2 day 4/21/00 → 2 day 4/26/00
necessary feature is done, removing keyword. need updated description of what exactly needs to be fixed.
Summary: [feature] Fix Stack z order → Fix Stack z order
Whiteboard: 2 day 4/26/00 → Need updated description of exactly what needs fixing.
1) If you place 2 views on top of each other in a stack. You can not click through them to any content underneath. 2) Any content lower on the stack that has views will appear to be on top on anything later in the stack both visually and mousewise. This is not what is expected and will cause major problems when people start using views in stacks. Examples are anything with opacity, splitters, or iframes.
Whiteboard: Need updated description of exactly what needs fixing.
nominating for nsbeta2. you can nsbeta2+ this, or wait for multiple bugs on symptoms caused by this...
Keywords: nsbeta2
[nsbeta2+]
Whiteboard: [nsbeta2+]
Blocks: 35442
Blocks: 40158
Mass-moving undated nsbeta2+ bugs to M18
Target Milestone: M16 → M18
spoke with evaughan, this will take a lot of work and a lot of widespread changes to fix. i really don't think a) the work will be done by mid-july and b) we want to land such big changes before mid-july. nominating for beta3, removing from beta2 radar, pushing to m21
Keywords: nsbeta3
Whiteboard: [nsbeta2+]
Target Milestone: M18 → M21
Whiteboard: [nsbeta2-]
Why would we hold the release for this bug?
nsbeta3-, aqua can wait.
Whiteboard: [nsbeta2-] → [nsbeta2-][nsbeta3-]
Target Milestone: M21 → Future
I suspect this is caused by the same thing: given the following xul: <stack> <vbox> <box height="100"/> <splitter height="10px"/> <box height="100"/> </vbox> <bulletinboard> <text top="100" value="this is a line of text"/> </bulletinboard> </stack> the splitter hides the line of text, which should be visible.
Keywords: skins
targeting
Target Milestone: Future → mozilla0.8
->moz0.9
Target Milestone: mozilla0.8 → mozilla0.9
->moz1.1
Target Milestone: mozilla0.9 → mozilla1.1
Blocks: 44513
*** Bug 70787 has been marked as a duplicate of this bug. ***
No longer blocks: 40158
Target Milestone: mozilla1.1alpha → ---
Decreasing the priority as no update for the last 2 years on this bug. See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage about the priority meaning.
Priority: P1 → P5

The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.

Assignee: eric → nobody
Status: ASSIGNED → NEW
Severity: normal → S3

old xul bug, closing

Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.