Closed Bug 21226 Opened 25 years ago Closed 24 years ago

Popupanchor/popupalign attributes don't work for <popup> tag

Categories

(Core :: XUL, defect, P3)

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

Tracking

()

Status:
RESOLVED FIXED
Milestone:
Future

People

(Reporter: cmanske, Assigned: mikepinkerton)

References

Details

We should be able to control the location of the popup window using the
"popupanchor" attribute -- for example, "popupanchor='bottomleft'" should place
the upper left corner of the popup window at the bottom-left corner of the
launching button.
Note that this works for <menupopup>. Just <popup> doesn't work.
Status: NEW → ASSIGNED
Summary: Popupanchor attribute doesn't work for <popup> tag → Popupanchor/popupalign attributes don't work for <popup> tag
Note to self: need to not pass in the screen coords in this case.
Target Milestone: M14
Assignee: hyatt → pinkerton
Status: ASSIGNED → NEW
Taking menu/popup bugs.
QA Contact: claudius → sairuh
Pink just took ownership of several menu-related bugs, most were already QAassigned to sairuh, I'm just making sure that they
all are now :-)
*** Bug 8925 has been marked as a duplicate of this bug. ***
Putting on beta1 radar.
Keywords: beta1
bulk accepting xpmenu/popup bugs. sigh.
Status: NEW → ASSIGNED
Putting on PDT- radar for beta1.  Would not hold beta for this bug.
Whiteboard: [PDT-]
postbeta.
Target Milestone: M14 → M15
Target Milestone: M15 → M16
moving all defects not directly related to P0 beta2 features off to M18.
Target Milestone: M16 → M18
Mass moving M18 bugs to M19
Target Milestone: M18 → M19
pardon the spam: beta1 is long gone...removing this keyword. will soon replace
w/nsbeta2...
Keywords: beta1
QA Contact: sairuh → jrgm
Target Milestone: M19 → M20
Whiteboard: [PDT-]
Target Milestone: M20 → M21
futuring.
Target Milestone: M21 → Future
i'm pretty sure this works since we're doing something similar for the
autocomplete popups.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.