11088 - Inconsistent way of moving non-eWindowType_child windows

Status: RESOLVED INCOMPLETE

(Core :: Layout: Form Controls, defect)

Description

[Stuart Parmenter]

Currently things such as gfx combo boxes, when they pop up windows are calling
move with x and y coords relative to their parents.  Other things, such as xul
popups call move based on screen coords.  The only way to tell the different in
which way to move these is to see if one has a parent or not.  Xul popups should
soon have parents which will cause move to be broken.  We need to have gfx
widgets position any new non-eWindowType_child windows with global coords which
they can obtain by calling WidgetToSceen.

Comment 1

[Kevin McCluskey (gone)]

Rod, reassigning to you.

Repositioning the combo dropdown using absolute coordinates is straight forward.
But, there may be issues with the view system having a view that is positioned
with absolute coordinates.

Comment 2

[Jerry.Kirk]

I wasn't sure what to do in the mean time for Photon so I just Move the
Pop-Up offset from the current cursor position, since I don't have a
parent to offset from.

Comment 3

[rods (gone)]

Currently, the view system and the positioning of widgets are all relative to
their parents. It has not been a requirement that we support absolutely
positioned widgets. There are several approaches that can be used for pops ups
that would not impact the view system or require other changes. If this
resolution is unsatisfactory, call a meeting with Kevin, Patrick, myself, and
Hyatt. This is not a bug, it is a feature request that needs an indepth
discussion.

Comment 4

[Stuart Parmenter]

this is a bug.  there are two different groups doing two different things which
will cause major confusing.  We should probably have a meeting to discuss this.
Does anyone have a particular time when would be good?

Comment 5

[Mike Pinkerton (not reading bugmail)]

Rod, remember that all feature requests to your group are now bugs. ;) what _is_
a girl to do?

Comment 6

[Peter Trudelle]

Request or defect, it is still valid. clearing resolution.

Comment 7

[rods (gone)]

changing to later

Comment 8

[bsharma]

Updating QA contact.

Comment 9

[Blake Ross]

reopening and marking Future...

Comment 10

[Vladimir Ermakov]

QA Contact Update

Comment 11

[Timea Cernea [:tbabos][inactive]]

Closing this as resolved:incomplete given the last real activity on this issue was 23 years ago and it is most likely not relevant anymore today. Please re-open it if you consider otherwise tho, thanks!