Another issue: The combobox popup opens at wrong place, if you scroll the
browser. This error occures in both browsers, IE and FF. Sorry for beeing
late with this, I saw it now.



Hugh Gibson wrote:
> 
>> Firefox:
>> If you scroll the browser (not the table widget), the selected row 
>> is not the row where the mouse pointer is. Instad a row is selected,
>> which is [scrolled pixel] below mouse pointer.
>> This works well in IE - at least in IE6. (Please could someone give
>> feedback, if the application runs in IE7?)
> 
> Works fine in IE7. 
> 
>> Internet Explorer 6:
>> - A double click in a table row opens a qx.ui.window.Window with an 
>> Iframe inside. But the underlaying browser window has an advertising
>> box in the right, and inside is a combobox ("Geschlecht"). This
>> combobox is not covered by the qooxdoo window.
> 
> OK in IE7.
> 
>> - If you select a combobox (Kategorie or Unterkategorie), the popup 
>> of the combo appears for a very shot time in the right of browser
>> window. This lets the application display flicker... not nice, but
>> not really terrible.
>> Also something like this happens in firefox too, but it's outside 
>> the visible area. Only the horizontal scollbar appears for a short
>> time.
> 
> Same here. Might be due to this code in qx.ui.popup.Popup._beforeAppear:
> 
>       if (this.getRestrictToPageOnOpen())
>       {
>         this._wantedLeft = this.getLeft();
> 
>         if (this._wantedLeft != null)
>         {
> // Move the popup out of the view so its size could be
> calculated before
>           // it is positioned.
>           this.setLeft(10000);
> 
>           if (this.getElement() != null)
>           {
>             // The popup was already visible once before
>             // -> Move it immediately before it gets visible again
>             this.getElement().style.left = 10000;
>           }
>         }
>       }
> 
> Might be worth trying to set restrictToPageOnOpen false for the popup
> window in the combo box.
> 
> Regarding the other problems, the best way to get help is to build a
> sample application that shows the problem. Then it's easier to debug. It
> might even help if you did a release build with linefeeds in it - then
> some work could be done on tracking down the issues with your app online.
> 
> Hugh
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
> 
> 

-- 
View this message in context: 
http://www.nabble.com/table-row-select-bug-%28FF%29-and-other-%28smaller%29-probs-with-online-app-tf4391216.html#a12561364
Sent from the qooxdoo-devel mailing list archive at Nabble.com.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to