Closed
Bug 8877
Opened 25 years ago
Closed 25 years ago
[FEATURE]Mozilla wants to support window z-order
Categories
(Core :: XUL, enhancement, P3)
Core
XUL
Tracking
()
VERIFIED
FIXED
M15
People
(Reporter: danm.moz, Assigned: danm.moz)
References
Details
Top level windows need to support z-ordering. This is a customer feature request for enabling things like
floating toolbars. It's also necessary for supporting the Navigator 4 "alwaysLowered" and "alwaysRaised"
window.open features.
Assignee: danm → don
Component: Browser-General → XPApps
QA Contact: leger → beppe
Comment 2•25 years ago
|
||
Wouldn't this belong in the XPToolkit?
Yep it is an XPToolkit issue. It should be noted that no one ever came up with a
web page that used the alwaysLowered or alwaysRaised window flag but I am sure
there is 1 customer on some intranet.
Updated•25 years ago
|
QA Contact: beppe → chrisd
Updated•25 years ago
|
Assignee: trudelle → danm
Target Milestone: M11
Comment 4•25 years ago
|
||
reassigning to danm, clearing target milestone
Updated•25 years ago
|
QA Contact: chrisd → claudius
Summary: AppRunner wants to support window z-order → [FEATURE]AppRunner wants to support window z-order
Whiteboard: [feature]
Updated•25 years ago
|
Whiteboard: 2 days
Comment 6•25 years ago
|
||
adding 2 days to swag & converting to expected landing date.
Whiteboard: 2 days → 3/31
Only implemented on Windows and the Mac (and keeping in mind Mac bugs 34540 and
34542, which aren't much of a problem for what we need z-ordering for today, but
will be a problem in the future.) I'm led to understand that the whole Window
Manager issue makes this nearly impossible on gtk, and our gtk zealot(s) aren't
certain they even want the functionality. Other platforms are on their own,
though most of the code behind this is cross-platform.
Calling it fixed.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Summary: [FEATURE]AppRunner wants to support window z-order → [FEATURE]Mozilla wants to support window z-order
Whiteboard: 3/31
You need to log in
before you can comment on or make changes to this bug.
Description
•