yes, it's the latest as of yesterday at about 4:30 EST (22 hours ago).
I've tried using the dom inspector and I think I'm seeing what the problem is.
If I look at the computed style for the dock layout, it's showing a zIndex of
'auto' event though further down in the tree (dock layout has a child
QxCanvasLayout that has the window as a child) I've got a window with zIndex
set to 100000. (The QxCanvasLayout of which the window is a child is also
showing a zIndex of 'auto').
Am I correct that this means getComputedStyle is broken with respect to zindex
calculation?
If so, the algorithm used to find the max zindex in bringToFront method of
QxPopup isn't going to work as it should.
I'd still be curious to know why the code (see "sloppy" code below) that I
inserted after that algorithm didn't work. Shouldn't the parent handling all
be done by the time bringToFront is called?
--Fred
On Wednesday 18 January 2006 02:10 pm, Sebastian Werner wrote:
> Fred,
>
> is this really true with the latest CVS? I really think all this stuff
> should be fixed. zIndex of QxPopup instances (which includes QxWindows,
> ...) is always >= 1e6.
>
> Sebastian
>
> Fred McDavid schrieb:
> > I've done some poking around. In ie6, where things are working as they
> > should, the zIndex is getting set to a large number (6 digits or so) when
> > the popup is displayed. In ff107, it's getting set to low single digits
> > (which increase by one every other time you press the drop-down button).
> >
> > Upon window creation, the zindex for the window is set to a 6 digit
> > number as well.
> >
> > I tried adding the following (sloppy) code at the end of bringToFront in
> > QxPopup (just before the last line which sets the zindex for the popup):
> >
> > QxWidget.flushGlobalQueues();
> > var offset = 1;
> > var compParent = true;
> > var p = this.getParent();
> > if (p)
> > {
> > //var pz = QxDom.getComputedStyleProperty(p.getElement(),'zIndex');
> > var pz = p.getZIndex();
> > while ((compParent)&&(typeof(pz) != 'number'))
> > {
> > p = p.getParent();
> > if (p)
> > {
> > //pz = QxDom.getComputedStyleProperty(p.getElement(),'zIndex');
> > var pz = p.getZIndex();
> > offset++;
> > }
> > else
> > {
> > compParent = false;
> > }
> > }
> > window.top.MDDebug(248,'info','QxPopup::bringToFront','pz: ' + pz +
> > ', vmax: ' + vMax);
> > if ((compParent)&&(vMax < pz))
> > {
> > vMax = pz+offset;
> > }
> > }
> >
> > when called, the debug statement reports that pz is null...implying that
> > it found a null parent at some point in the loop prior to finding a
> > numeric ancestral zIndex.
> >
> > if I comment out the calls in the above code to getZIndex and replace
> > them with the QxDom-based calls above them, the debug statement reports
> > that pz is 'auto'
> >
> > In the QxPopup bringToFront method, it looks like it's trying to find the
> > max zindex from the top down...could it be that QxDockLayout is not
> > reporting it's zindex style property correctly?
> >
> > Anyway, just hoping you might have comments or suggestions.
> >
> > Thanks and regards,
> >
> > --Fred
> >
> > On Wednesday 18 January 2006 02:58 am, Sebastian Werner wrote:
> >> Fred McDavid schrieb:
> >>> On Wednesday 18 January 2006 01:13 am, Sebastian Werner wrote:
> >>>> Fred McDavid schrieb:
> >>>>> Hi Sebastian,
> >>>>>
> >>>>> I've hacked up Window_5.html example to illustrate the issue.
> >>>>>
> >>>>> The combo box on tab 1 behaves normally until the window is placed in
> >>>>> the main area of the QxDockLayout.
> >>>>
> >>>> What do you mean with "placed" here? As I can see there is a
> >>>> QxDockLayout which is stretching to the document/window size. So the
> >>>> window is always placed in the main area.
> >>>
> >>> that is, if I forget the dock layout and add the window to the
> >>> document, everything is fine, but if I add a dock layout to the
> >>> document, then add the window to the docklayout's main rendering area,
> >>> then the combobox popup appears under the window (but above the
> >>> docklayout rendering area).
> >>
> >> Should the example you send show the problem directly, or must I change
> >> something there first? I could not reproduce it here. That's my problem.
> >>
> >>>> Or do you mean you add the QxWindow to the QxDockLayout?
> >>>>
> >>>> I don't see any misbehaviour. But probably I simply don't understand
> >>>> what you mean. Is this also reproduceable with a current Firefox 1.5
> >>>> (I am using this version)?
> >>>
> >>> I'm using firefox v1.0.7 and I've attached a screenshot showing the
> >>> issue.
> >>
> >> This was what I expected from your description. But I don't know how to
> >> reproduce it here.
> >>
> >>> I'll try to figure it out and submit a patch...was just hoping it was
> >>> something easy :)
> >>
> >> That would be really nice.
> >>
> >> Sebastian
> >>
> >>> --Fred
> >>>
> >>>>> When I do that, the popup appears beneath the
> >>>>> window...unless you're working with windows that hide the popup like
> >>>>> I've been for the past few days :)
> >>>>>
> >>>>> Browser id:
> >>>>>
> >>>>> Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922
> >>>>>
> >>>>> In ie6, combobox behavior is normal.
> >>>>>
> >>>>> --Fred
> >>>>
> >>>> -------------------------------------------------------
> >>>> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> >>>> files for problems? Stop! Download the new AJAX search engine that
> >>>> makes searching your log files as easy as surfing the web. DOWNLOAD
> >>>> SPLUNK!
> >>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=1216
> >>>>42 _______________________________________________
> >>>> Qooxdoo-devel mailing list
> >>>> [email protected]
> >>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
> >>>
> >>> -----------------------------------------------------------------------
> >>>-
> >>
> >> -------------------------------------------------------
> >> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> >> files for problems? Stop! Download the new AJAX search engine that
> >> makes searching your log files as easy as surfing the web. DOWNLOAD
> >> SPLUNK!
> >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> >> _______________________________________________
> >> Qooxdoo-devel mailing list
> >> [email protected]
> >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
--
==========================================================
Fred R. McDavid, III
540-248-0838
[EMAIL PROTECTED]
BitDaddy Systems, Inc
* Complex System Design, Management, and Hosting
==========================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
