- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Fri, 20 Sep 2013 18:58:04 +1200
- To: www-style <www-style@w3.org>
- Message-ID: <CAOp6jLb-LA-fLEhp6Hdv=LP0_wpBuGKS+fGt74sey=PZiPTYRw@mail.gmail.com>
On Fri, Sep 20, 2013 at 5:55 PM, Robert O'Callahan <robert@ocallahan.org>wrote: > What should getBoxQuads() on a table element return? Obvious options: > 1) a quad for the "inner table box" (the box with the rows and columns, > which has the table border on it) > 2) a quad for the "outer table box" (the box enclosing the inner table box > and any caption box, which has the table margins on it) > 3) a quad for the "inner table box" and a quad for the caption box > > For the analogous question with getClientRects(), Gecko currently does #3, > which is explicitly mandated as a special case in the CSSOM Views spec: > http://dev.w3.org/csswg/cssom-view/#dom-element-getclientrects > I think the rationale is that we want getBoundingClientRect() on a table > to include the caption area, but option #2 (which is what Chrome > getClientRects() does) doesn't match the box where the border is drawn and > doesn't give you a way to get the inner table box geometry). > > In a way, the most logical thing to do for getBoxQuads would be to use the > inner table box for "content", "padding" and "border" boxes and use the > outer table box for "margin" boxes and ignore the caption altogether, but > that could still confuse authors. I'm not sure what to do, other than curse > tables. > I'm leaning towards the choice in the last paragraph. It's the closest match to reality. Rob -- Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehrotraiitny eovni le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o Whhei csha iids teoa stiheer :p atroa lsyazye,d 'mYaonu,r "sGients uapr,e tfaokreg iyvoeunr, 'm aotr atnod sgaoy ,h o'mGee.t" uTph eann dt hwea lmka'n? gBoutt uIp waanndt wyeonut thoo mken.o w * *
Received on Friday, 20 September 2013 06:58:32 UTC