Don't repeat thead if the first row exceeds the height of the page
BUG=669690
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Committed: https://crrev.com/6287f21e89cc890abab98237d7b1a0d51f649221
Cr-Commit-Position: refs/heads/master@{#438084}
Dry run: Try jobs failed on following builders: linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_rel_ng/builds/349429)
HI mstensho,
https://drafts.csswg.org/css-tables-3/#repeated-headers says not to repeat
headers if the first content row exceeds the height of the page. This conflicts
with what we do when we handle repeating headers on a table nested inside a
content row.
What is the correct behaviour here in your opinion?
Rendering the nested headers like we do in the now-failing tests seems
reasonable to me.
mstensho (USE GERRIT)
On 2016/12/03 18:06:41, rhogan wrote: > HI mstensho, > > https://drafts.csswg.org/css-tables-3/#repeated-headers says not to repeat ...
On 2016/12/03 18:06:41, rhogan wrote:
> HI mstensho,
>
> https://drafts.csswg.org/css-tables-3/#repeated-headers says not to repeat
> headers if the first content row exceeds the height of the page. This
conflicts
> with what we do when we handle repeating headers on a table nested inside a
> content row.
>
> What is the correct behaviour here in your opinion?
>
> Rendering the nested headers like we do in the now-failing tests seems
> reasonable to me.
With the code changes, those tests still leave room in each column for the
header of the outer table, which seems wrong (since it's not painted). Other
than that, I find it reasonable to disallow repeating headers if the TBODY rows
are too tall.
rhogan
On 2016/12/05 at 11:41:00, mstensho wrote: > With the code changes, those tests still leave ...
On 2016/12/05 at 11:41:00, mstensho wrote:
> With the code changes, those tests still leave room in each column for the
header of the outer table, which seems wrong (since it's not painted). Other
than that, I find it reasonable to disallow repeating headers if the TBODY rows
are too tall.
So should I just remove the code that deals with repeating headers in nested
tables? By definition if a table is inside a row and extends over more than one
page we're not allowed to repeat its header. If we are still to paint the nested
header it doesn't seem right to paint it in the same position as the outer
table's header, does it?
mstensho (USE GERRIT)
On 2016/12/05 18:50:19, rhogan wrote: > On 2016/12/05 at 11:41:00, mstensho wrote: > > With ...
On 2016/12/05 18:50:19, rhogan wrote:
> On 2016/12/05 at 11:41:00, mstensho wrote:
> > With the code changes, those tests still leave room in each column for the
> header of the outer table, which seems wrong (since it's not painted). Other
> than that, I find it reasonable to disallow repeating headers if the TBODY
rows
> are too tall.
>
> So should I just remove the code that deals with repeating headers in nested
> tables? By definition if a table is inside a row and extends over more than
one
> page we're not allowed to repeat its header. If we are still to paint the
nested
> header it doesn't seem right to paint it in the same position as the outer
> table's header, does it?
That sounds good. Just remove support for nesting and only repeat the inner
header? That should simplify the code a bit as well, I suppose.
rhogan
Should I repeat it at the same y pos as the outer header though? That ...
Should I repeat it at the same y pos as the outer header though? That seems
potentially confusing.
On Tue, 6 Dec 2016 17:42 , <mstensho@opera.com> wrote:
> On 2016/12/05 18:50:19, rhogan wrote:
> > On 2016/12/05 at 11:41:00, mstensho wrote:
> > > With the code changes, those tests still leave room in each column for
> the
> > header of the outer table, which seems wrong (since it's not painted).
> Other
> > than that, I find it reasonable to disallow repeating headers if the
> TBODY
> rows
> > are too tall.
> >
> > So should I just remove the code that deals with repeating headers in
> nested
> > tables? By definition if a table is inside a row and extends over more
> than
> one
> > page we're not allowed to repeat its header. If we are still to paint the
> nested
> > header it doesn't seem right to paint it in the same position as the
> outer
> > table's header, does it?
>
> That sounds good. Just remove support for nesting and only repeat the inner
> header? That should simplify the code a bit as well, I suppose.
>
> https://codereview.chromium.org/2545243002/
>
--
You received this message because you are subscribed to the Google Groups "Blink
Reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-reviews+unsubscribe@chromium.org.
rhogan
Should I repeat it at the same y pos as the outer header though? That ...
Should I repeat it at the same y pos as the outer header though? That seems
potentially confusing.
On Tue, 6 Dec 2016 17:42 , <mstensho@opera.com> wrote:
> On 2016/12/05 18:50:19, rhogan wrote:
> > On 2016/12/05 at 11:41:00, mstensho wrote:
> > > With the code changes, those tests still leave room in each column for
> the
> > header of the outer table, which seems wrong (since it's not painted).
> Other
> > than that, I find it reasonable to disallow repeating headers if the
> TBODY
> rows
> > are too tall.
> >
> > So should I just remove the code that deals with repeating headers in
> nested
> > tables? By definition if a table is inside a row and extends over more
> than
> one
> > page we're not allowed to repeat its header. If we are still to paint the
> nested
> > header it doesn't seem right to paint it in the same position as the
> outer
> > table's header, does it?
>
> That sounds good. Just remove support for nesting and only repeat the inner
> header? That should simplify the code a bit as well, I suppose.
>
> https://codereview.chromium.org/2545243002/
>
--
You received this message because you are subscribed to the Google Groups
"Chromium-reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.
mstensho (USE GERRIT)
On 2016/12/06 17:46:47, rhogan wrote: > Should I repeat it at the same y pos ...
On 2016/12/06 17:46:47, rhogan wrote:
> Should I repeat it at the same y pos as the outer header though? That seems
> potentially confusing.
At the top of every fragmentainer involved. Is there any other option?
rhogan
Yes I guess you're right! On Tue, 6 Dec 2016 17:49 , <mstensho@opera.com> wrote: > ...
Yes I guess you're right!
On Tue, 6 Dec 2016 17:49 , <mstensho@opera.com> wrote:
> On 2016/12/06 17:46:47, rhogan wrote:
> > Should I repeat it at the same y pos as the outer header though? That
> seems
> > potentially confusing.
>
> At the top of every fragmentainer involved. Is there any other option?
>
> https://codereview.chromium.org/2545243002/
>
--
You received this message because you are subscribed to the Google Groups "Blink
Reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-reviews+unsubscribe@chromium.org.
rhogan
Yes I guess you're right! On Tue, 6 Dec 2016 17:49 , <mstensho@opera.com> wrote: > ...
Yes I guess you're right!
On Tue, 6 Dec 2016 17:49 , <mstensho@opera.com> wrote:
> On 2016/12/06 17:46:47, rhogan wrote:
> > Should I repeat it at the same y pos as the outer header though? That
> seems
> > potentially confusing.
>
> At the top of every fragmentainer involved. Is there any other option?
>
> https://codereview.chromium.org/2545243002/
>
--
You received this message because you are subscribed to the Google Groups
"Chromium-reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.
rhogan
Description was changed from ========== Don't repeat thead if the first row exceeds the height ...
Description was changed from
==========
Don't repeat thead if the first row exceeds the height of the page
BUG=669690
==========
to
==========
Don't repeat thead if the first row exceeds the height of the page
BUG=669690
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
==========
rhogan
The CQ bit was checked by robhogan@gmail.com to run a CQ dry run
Dry run: Try jobs failed on following builders: win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_ng/builds/347765)
Dry run: Try jobs failed on following builders: linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/196708)
Description was changed from
==========
Don't repeat thead if the first row exceeds the height of the page
BUG=669690
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
==========
to
==========
Don't repeat thead if the first row exceeds the height of the page
BUG=669690
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Review-Url: https://codereview.chromium.org/2545243002
==========
Description was changed from
==========
Don't repeat thead if the first row exceeds the height of the page
BUG=669690
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Review-Url: https://codereview.chromium.org/2545243002
==========
to
==========
Don't repeat thead if the first row exceeds the height of the page
BUG=669690
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Committed: https://crrev.com/6287f21e89cc890abab98237d7b1a0d51f649221
Cr-Commit-Position: refs/heads/master@{#438084}
==========
commit-bot: I haz the power
Patchset 4 (id:??) landed as https://crrev.com/6287f21e89cc890abab98237d7b1a0d51f649221 Cr-Commit-Position: refs/heads/master@{#438084}
Issue 2545243002: Don't repeat thead if the first row exceeds the height of the page
(Closed)
Created 4 years ago by rhogan
Modified 4 years ago
Reviewers: mstensho (USE GERRIT)
Base URL:
Comments: 3