Closed
Bug 577377
Opened 16 years ago
Closed 15 years ago
Provide a means of retrieving the screen rectangle of a popup
Categories
(Core :: XUL, defect)
Core
XUL
Tracking
()
RESOLVED
FIXED
People
(Reporter: enndeakin, Assigned: enndeakin)
References
Details
Attachments
(1 file, 2 obsolete files)
|
9.22 KB,
patch
|
neil
:
review+
|
Details | Diff | Splinter Review |
With titlebars present on a popup, there is a need to have a way to get the screen position and size including window decorations of the popup. The usual screen coordinate retrieval methods return the position and size without decorations.
| Assignee | ||
Comment 1•15 years ago
|
||
Attachment #456348 -
Attachment is obsolete: true
Attachment #520627 -
Flags: review?(neil)
Comment 2•15 years ago
|
||
Comment on attachment 520627 [details] [diff] [review]
fix up whitespace
This doesn't work in a popupshowing handler.
In the case of a standalone popup, the rectangle returned is that from when the popup was last shown.
In the case of a popup attached to a menu, the rectangle returned is also wrong, but in a different way which I didn't investigate further.
Attachment #520627 -
Flags: review?(neil) → review-
| Assignee | ||
Comment 3•15 years ago
|
||
Attachment #520627 -
Attachment is obsolete: true
Attachment #525728 -
Flags: review?(neil)
| Assignee | ||
Comment 4•15 years ago
|
||
The views and widgets are set to 0,0 size while closed, so the value during a popupshowing handler isn't valid. So here I just always set the rectangle to (0,0,0,0) during popupshowing.
Updated•15 years ago
|
Attachment #525728 -
Flags: review?(neil) → review+
| Assignee | ||
Updated•15 years ago
|
Keywords: checkin-needed
Comment 5•15 years ago
|
||
Neil, please put metadata in your checkin-needed patches?
| Assignee | ||
Updated•15 years ago
|
Keywords: checkin-needed
| Assignee | ||
Comment 6•15 years ago
|
||
Status: NEW → RESOLVED
Closed: 15 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Updated•7 years ago
|
Component: XP Toolkit/Widgets: Menus → XUL
You need to log in
before you can comment on or make changes to this bug.
Description
•