Hello qooxdoo community, being new to this mailing list let me first say >Thank You< for creating this wonderful piece of software!
Within a project where the document retrieval as part of a DMS is being realized as a qooxdoo 0.6.6 based web application (with a PHP DB-backend), our customer encountered a problem where the lists (made up by qx.ui.table.Table) seem to be buggy only within a certain system environment. While during development Firefox is our web browser of choice, due to administrative reasons we are bound to support IE6 at our customers place. All Windows XP workstations there (lots of them) do their job flawlessly, while the few old Windows 2000 workstations do fail at a certain point when it comes to render tables with vertical scroll bars. When dragging the bar(s) (at a certain speed!), the browser does crash. I was able to reproduce this problem. Using the scroll bar very gently, giving the browser a chance to render the rows one by one, everything seems to work fine. Especially when using a form with two tables with vertical scroll bars, the browser easily crashes when dragging one table's bar, then quickly the other one's. Sadly I cannot instruct our customer how to drag the scroll bars, so I have to find a fix. I searched the qooxdoo bug lists, but did not find this special issue covered there; I thought to have found a similarity in bug#317 and tried the suggested workaround, but without success. Further on I had hoped to find this issue resolved within qooxdoo 0.7, but today, when testing on the new qooxdoo Demo Browser, I found IE6 crash when trying the Table 1 and Table 2 widgets (Table 3 using up so much CPU time on my test machine that a quick rendering seems impossible anyway, maybe thus preventing the crash, which might lead to the suspicion of the browser rendering engine being broken). While, as I stated before, this problem does not persist on Windows XP (tested with IE 6.0.2900.2180.xpsp_sp2) and not on Firefox (any tested version), there seems to be an as yet unadressed bug of qx.ui.table.Table within Windows 2000 (SP4)'s standard IE 6.0.2800.1106 (SP1 with several updates). As I found this problem on any Win2k machine I could test, while no update seemed to fix it, I ask if any reader here knows of this problem and maybe even of a fix to it. To reproduce the effect, just take a machine with the OS and browser mentioned before and start any qooxdoo table demo with a vertical scroll bar (like http://demo.qooxdoo.org/current/demobrowser/#example~Table_2.html) . Drag the bar quickly up and down and watch the browser error message pop up. Please have in mind that I was only able to test on rather slowish machines (Pentium III 800Mhz class notebook like, 128MB RAM, IE eating up ~ 70 megs within the demo). I'd be interested to know if this effect did not happen on fast or extra slow systems. As I'm inexperienced in what effects being defined as a bug in the qooxdoo context, I'd rather post my thoughts here that committing a bug to that special list (I'd do that if I was more certain about the circumstances). Please forgive me if this is inappropriate. Any help appreciated, thx in advance, Stefan ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
