[Bug 26464] New: Parsing of Table Cells: Calculated Height CSS Attribute

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26464

            Bug ID: 26464
           Summary: Parsing of Table Cells: Calculated Height CSS
                    Attribute
           Product: HTML.next
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: default
          Assignee: dave.null@w3.org
          Reporter: seamus@mulholland.eu
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, robin@w3.org

Presently in Google Chrome the calculated CSS height attributes of all table
cells within a table row are equal with each table cell having a height
attribute equal to the height of the tallest cell in the table row. In Internet
Explorer and Firefox the calculated CSS height attribute of each table cell
within a table row is different with each table cell having a height attribute
reflective of the height of the content contained within the cell. Perhaps
going forward it would be preferable to follow Google Chrome's lead. Then each
cell within the row would allow for child elements contained within the cells
to be fitted to the available space by setting the table cell's CSS position
attribute to relative and then the CSS position attribute of the contained
child element to absolute such that the child can take on it's parent table
cell's CSS width and CSS height attributes. This seems like a sensible course
to take considering that users seeking the CSS height value of the content
contained within a cell could simply wrap the content in a div wrapper. Perhaps
there could even be a CSS content-height attribute?

As I say Google Chrome already has taken-on this approach, and the benefit is
as set-out in the above paragraph, namely that after a long time there finally
is a solution in Google Chrome to getting child elements to fill-out the
available space within a parent table cell.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 30 July 2014 00:53:50 UTC