I use tables a lot too, and this section of the app works fine if I extract
it into a standalone application, so I agree with you that it's not a bug in
Qooxdoo's table implementation (this happens when only using the default
cell renders).
What's happening is that Chrome is ignoring the "qooxdoo-table-cell" CSS
class that is on the table cell's DIV.
If you hover over the DIV in the debugger's "Elements" pane, it highlights
where the DIV really is in this case the cell is hidden below the table.
This is exactly the behaviour you get if you remove the qooxdoo-table-cell
class from the DIV.
I've found that if qx.bom.Stylesheet.createElement uses sheet.insertRule to
add a dummy rule at the start of the stylesheet, the problem is fixed.
John.
From: Derrell Lipman <[email protected]>
Reply-To: qooxdoo Development <[email protected]>
Date: Fri, 20 Apr 2012 11:44:54 -0400
To: qooxdoo Development <[email protected]>
Subject: Re: [qooxdoo-devel] Table display problems in Chrome
On Fri, Apr 20, 2012 at 11:38, John Spackman <[email protected]> wrote:
> Hi Derrell
>
> Pretty sure but the table redraws itself if I click on the table cell's DIV
> in the debugger; I can see before I click on it that type CSS is correct but
> hovering the mouse over the DIV highlights it's position as underneath the
> table, and once I click on the element in the debugger the div repositions
> itself.
>
> I think that this is something to do with dynamically-added stylesheets not
> being interpreted (the table used stylesheets for cells); if I do this in the
> javascript console:
> var sheet = qx.bom.Stylesheet.createElement(".stuff { font-weight: inherit; }
> ");
> qx.bom.Stylesheet.addRule(sheet, ".more-stuff", "font-weight: inherit;");
>
> The second line makes the table cells appear.
I'm not sure what's causing your problem. I use Table extensively in Chrome
(on Linux) and have no difficulty with it rendering everything, which would
lead me to believe there is not a generic bug in the implementation. The
area we discussing, though, is cell renderers, and you may be using some
that I am not. Although it will obviously improperly display your data, the
first thing I'd do to debug that is to get rid of all of your assignments of
cell renderers, so that all cells are rendered using the default cell
renderer. If that solves the problem, then put them back in one by one,
until you find the guilty culprit.
Cheers,
Derrell
----------------------------------------------------------------------------
-- For Developers, A Lot Can Happen In A Second. Boundary is the first to
Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try
it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2_________________________________________
______ qooxdoo-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
