Intent to unship: rowspan=0

classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|

Intent to unship: rowspan=0

Manish Goregaokar
Gecko (and previously Presto) support setting `rowspan=0` in non-quirksmode
documents to mean "up to the end of the rowgroup" (for rows not within
rowgroups, this means that it spans up to the next rowgroup or the end of
the table). It is equivalent to setting rowspan to a very large number.

colspan=0 does not do this[1]

Chrome/Blink very recently added support[2], but it's still in Canary, and
I'd like to remove it from both browsers and the spec before it hits
release.

You can already achieve this behavior with `rowspan=<large number>`, and we
should encourage developers to use Grid anyway, so I don't see much value
in having this feature in and of itself. Given that it was only supported
by one browser (us) for so many years, it's questionable whether it's used
enough on the Web for it to be something we must keep for compat reasons.

Thoughts?

 [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1241840
 [2]: https://bugs.chromium.org/p/chromium/issues/detail?id=180722


-Manish Goregaokar
_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: Intent to unship: rowspan=0

Manish Goregaokar
(Of course, this is contingent on the Chrome people agreeing to unship this
as well)

-Manish Goregaokar

On Tue, Feb 27, 2018 at 2:28 PM, Manish Goregaokar <[hidden email]>
wrote:

> Gecko (and previously Presto) support setting `rowspan=0` in
> non-quirksmode documents to mean "up to the end of the rowgroup" (for rows
> not within rowgroups, this means that it spans up to the next rowgroup or
> the end of the table). It is equivalent to setting rowspan to a very large
> number.
>
> colspan=0 does not do this[1]
>
> Chrome/Blink very recently added support[2], but it's still in Canary, and
> I'd like to remove it from both browsers and the spec before it hits
> release.
>
> You can already achieve this behavior with `rowspan=<large number>`, and
> we should encourage developers to use Grid anyway, so I don't see much
> value in having this feature in and of itself. Given that it was only
> supported by one browser (us) for so many years, it's questionable whether
> it's used enough on the Web for it to be something we must keep for compat
> reasons.
>
> Thoughts?
>
>  [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1241840
>  [2]: https://bugs.chromium.org/p/chromium/issues/detail?id=180722
>
>
> -Manish Goregaokar
>
_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: Intent to unship: rowspan=0

Emilio Cobos Álvarez
Hi Manish,

Can you open / link to a bug for this work?

Also, is it on the spec? If so, probably spec issues need to be filed if
we really want it to get dropped?

A bit of reasoning (I do know why from IRC, but you should probably
explain) about why would be helpful, too.

It is indeed unfortunate that Blink added support for this just a month
before you intend to remove it, but probably as long as they're willing
to not ship it is fine.

Thanks,

  -- Emilio

On 02/27/2018 11:31 PM, Manish Goregaokar wrote:

> (Of course, this is contingent on the Chrome people agreeing to unship this
> as well)
>
> -Manish Goregaokar
>
> On Tue, Feb 27, 2018 at 2:28 PM, Manish Goregaokar <[hidden email]>
> wrote:
>
>> Gecko (and previously Presto) support setting `rowspan=0` in
>> non-quirksmode documents to mean "up to the end of the rowgroup" (for rows
>> not within rowgroups, this means that it spans up to the next rowgroup or
>> the end of the table). It is equivalent to setting rowspan to a very large
>> number.
>>
>> colspan=0 does not do this[1]
>>
>> Chrome/Blink very recently added support[2], but it's still in Canary, and
>> I'd like to remove it from both browsers and the spec before it hits
>> release.
>>
>> You can already achieve this behavior with `rowspan=<large number>`, and
>> we should encourage developers to use Grid anyway, so I don't see much
>> value in having this feature in and of itself. Given that it was only
>> supported by one browser (us) for so many years, it's questionable whether
>> it's used enough on the Web for it to be something we must keep for compat
>> reasons.
>>
>> Thoughts?
>>
>>   [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1241840
>>   [2]: https://bugs.chromium.org/p/chromium/issues/detail?id=180722
>>
>>
>> -Manish Goregaokar
>>
> _______________________________________________
> dev-tech-layout mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-tech-layout
>
_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: Intent to unship: rowspan=0

Manish Goregaokar
Yeah, it's specced:
https://html.spec.whatwg.org/multipage/tables.html#attr-tdth-rowspan

Opened bug with same text here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1441710


I think the reasoning is in the email? Is there something more specific
you're looking for?

Thanks,

-Manish Goregaokar

On Tue, Feb 27, 2018 at 3:08 PM, Emilio Cobos Álvarez <[hidden email]>
wrote:

> Hi Manish,
>
> Can you open / link to a bug for this work?
>
> Also, is it on the spec? If so, probably spec issues need to be filed if
> we really want it to get dropped?
>
> A bit of reasoning (I do know why from IRC, but you should probably
> explain) about why would be helpful, too.
>
> It is indeed unfortunate that Blink added support for this just a month
> before you intend to remove it, but probably as long as they're willing to
> not ship it is fine.
>
> Thanks,
>
>  -- Emilio
>
>
> On 02/27/2018 11:31 PM, Manish Goregaokar wrote:
>
>> (Of course, this is contingent on the Chrome people agreeing to unship
>> this
>> as well)
>>
>> -Manish Goregaokar
>>
>> On Tue, Feb 27, 2018 at 2:28 PM, Manish Goregaokar <[hidden email]
>> >
>> wrote:
>>
>> Gecko (and previously Presto) support setting `rowspan=0` in
>>> non-quirksmode documents to mean "up to the end of the rowgroup" (for
>>> rows
>>> not within rowgroups, this means that it spans up to the next rowgroup or
>>> the end of the table). It is equivalent to setting rowspan to a very
>>> large
>>> number.
>>>
>>> colspan=0 does not do this[1]
>>>
>>> Chrome/Blink very recently added support[2], but it's still in Canary,
>>> and
>>> I'd like to remove it from both browsers and the spec before it hits
>>> release.
>>>
>>> You can already achieve this behavior with `rowspan=<large number>`, and
>>> we should encourage developers to use Grid anyway, so I don't see much
>>> value in having this feature in and of itself. Given that it was only
>>> supported by one browser (us) for so many years, it's questionable
>>> whether
>>> it's used enough on the Web for it to be something we must keep for
>>> compat
>>> reasons.
>>>
>>> Thoughts?
>>>
>>>   [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1241840
>>>   [2]: https://bugs.chromium.org/p/chromium/issues/detail?id=180722
>>>
>>>
>>> -Manish Goregaokar
>>>
>>> _______________________________________________
>> dev-tech-layout mailing list
>> [hidden email]
>> https://lists.mozilla.org/listinfo/dev-tech-layout
>>
>> _______________________________________________
> dev-tech-layout mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-tech-layout
>
_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: Intent to unship: rowspan=0

Emilio Cobos Álvarez
On 02/28/2018 12:28 AM, Manish Goregaokar wrote:
> Yeah, it's specced:
> https://html.spec.whatwg.org/multipage/tables.html#attr-tdth-rowspan
>
> Opened bug with same text here:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1441710

Thanks!

> I think the reasoning is in the email? Is there something more specific
> you're looking for?

Yeah fair enough (I expected to mention your Servo table layout stuff,
but I guess that's more off-topic than on-topic), sorry :)

  -- Emilio

> Thanks,
>
> -Manish Goregaokar
>
> On Tue, Feb 27, 2018 at 3:08 PM, Emilio Cobos Álvarez <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     Hi Manish,
>
>     Can you open / link to a bug for this work?
>
>     Also, is it on the spec? If so, probably spec issues need to be
>     filed if we really want it to get dropped?
>
>     A bit of reasoning (I do know why from IRC, but you should probably
>     explain) about why would be helpful, too.
>
>     It is indeed unfortunate that Blink added support for this just a
>     month before you intend to remove it, but probably as long as
>     they're willing to not ship it is fine.
>
>     Thanks,
>
>       -- Emilio
>
>
>     On 02/27/2018 11:31 PM, Manish Goregaokar wrote:
>
>         (Of course, this is contingent on the Chrome people agreeing to
>         unship this
>         as well)
>
>         -Manish Goregaokar
>
>         On Tue, Feb 27, 2018 at 2:28 PM, Manish Goregaokar
>         <[hidden email] <mailto:[hidden email]>>
>         wrote:
>
>             Gecko (and previously Presto) support setting `rowspan=0` in
>             non-quirksmode documents to mean "up to the end of the
>             rowgroup" (for rows
>             not within rowgroups, this means that it spans up to the
>             next rowgroup or
>             the end of the table). It is equivalent to setting rowspan
>             to a very large
>             number.
>
>             colspan=0 does not do this[1]
>
>             Chrome/Blink very recently added support[2], but it's still
>             in Canary, and
>             I'd like to remove it from both browsers and the spec before
>             it hits
>             release.
>
>             You can already achieve this behavior with `rowspan=<large
>             number>`, and
>             we should encourage developers to use Grid anyway, so I
>             don't see much
>             value in having this feature in and of itself. Given that it
>             was only
>             supported by one browser (us) for so many years, it's
>             questionable whether
>             it's used enough on the Web for it to be something we must
>             keep for compat
>             reasons.
>
>             Thoughts?
>
>                [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1241840
>             <https://bugzilla.mozilla.org/show_bug.cgi?id=1241840>
>                [2]:
>             https://bugs.chromium.org/p/chromium/issues/detail?id=180722
>             <https://bugs.chromium.org/p/chromium/issues/detail?id=180722>
>
>
>             -Manish Goregaokar
>
>         _______________________________________________
>         dev-tech-layout mailing list
>         [hidden email]
>         <mailto:[hidden email]>
>         https://lists.mozilla.org/listinfo/dev-tech-layout
>         <https://lists.mozilla.org/listinfo/dev-tech-layout>
>
>     _______________________________________________
>     dev-tech-layout mailing list
>     [hidden email]
>     <mailto:[hidden email]>
>     https://lists.mozilla.org/listinfo/dev-tech-layout
>     <https://lists.mozilla.org/listinfo/dev-tech-layout>
>
>
_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: Intent to unship: rowspan=0

Manish Goregaokar
Yeah. Implementing it in servo is not a big deal -- we already (perhaps
accidentally) account for it in cell placement, we just don't handle it for
cell sizing, and that's an easy patch

On Feb 27, 2018 3:50 PM, "Emilio Cobos Álvarez" <[hidden email]> wrote:

> On 02/28/2018 12:28 AM, Manish Goregaokar wrote:
>
>> Yeah, it's specced: https://html.spec.whatwg.org/m
>> ultipage/tables.html#attr-tdth-rowspan
>>
>> Opened bug with same text here: https://bugzilla.mozilla.org/s
>> how_bug.cgi?id=1441710
>>
>
> Thanks!
>
> I think the reasoning is in the email? Is there something more specific
>> you're looking for?
>>
>
> Yeah fair enough (I expected to mention your Servo table layout stuff, but
> I guess that's more off-topic than on-topic), sorry :)
>
>  -- Emilio
>
> Thanks,
>>
>> -Manish Goregaokar
>>
>> On Tue, Feb 27, 2018 at 3:08 PM, Emilio Cobos Álvarez <[hidden email]
>> <mailto:[hidden email]>> wrote:
>>
>>     Hi Manish,
>>
>>     Can you open / link to a bug for this work?
>>
>>     Also, is it on the spec? If so, probably spec issues need to be
>>     filed if we really want it to get dropped?
>>
>>     A bit of reasoning (I do know why from IRC, but you should probably
>>     explain) about why would be helpful, too.
>>
>>     It is indeed unfortunate that Blink added support for this just a
>>     month before you intend to remove it, but probably as long as
>>     they're willing to not ship it is fine.
>>
>>     Thanks,
>>
>>       -- Emilio
>>
>>
>>     On 02/27/2018 11:31 PM, Manish Goregaokar wrote:
>>
>>         (Of course, this is contingent on the Chrome people agreeing to
>>         unship this
>>         as well)
>>
>>         -Manish Goregaokar
>>
>>         On Tue, Feb 27, 2018 at 2:28 PM, Manish Goregaokar
>>         <[hidden email] <mailto:[hidden email]>>
>>         wrote:
>>
>>             Gecko (and previously Presto) support setting `rowspan=0` in
>>             non-quirksmode documents to mean "up to the end of the
>>             rowgroup" (for rows
>>             not within rowgroups, this means that it spans up to the
>>             next rowgroup or
>>             the end of the table). It is equivalent to setting rowspan
>>             to a very large
>>             number.
>>
>>             colspan=0 does not do this[1]
>>
>>             Chrome/Blink very recently added support[2], but it's still
>>             in Canary, and
>>             I'd like to remove it from both browsers and the spec before
>>             it hits
>>             release.
>>
>>             You can already achieve this behavior with `rowspan=<large
>>             number>`, and
>>             we should encourage developers to use Grid anyway, so I
>>             don't see much
>>             value in having this feature in and of itself. Given that it
>>             was only
>>             supported by one browser (us) for so many years, it's
>>             questionable whether
>>             it's used enough on the Web for it to be something we must
>>             keep for compat
>>             reasons.
>>
>>             Thoughts?
>>
>>                [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1241840
>>             <https://bugzilla.mozilla.org/show_bug.cgi?id=1241840>
>>                [2]:
>>             https://bugs.chromium.org/p/chromium/issues/detail?id=180722
>>             <https://bugs.chromium.org/p/chromium/issues/detail?id=180722
>> >
>>
>>
>>             -Manish Goregaokar
>>
>>         _______________________________________________
>>         dev-tech-layout mailing list
>>         [hidden email]
>>         <mailto:[hidden email]>
>>         https://lists.mozilla.org/listinfo/dev-tech-layout
>>         <https://lists.mozilla.org/listinfo/dev-tech-layout>
>>
>>     _______________________________________________
>>     dev-tech-layout mailing list
>>     [hidden email]
>>     <mailto:[hidden email]>
>>     https://lists.mozilla.org/listinfo/dev-tech-layout
>>     <https://lists.mozilla.org/listinfo/dev-tech-layout>
>>
>>
>>
_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: Intent to unship: rowspan=0

Boris Zbarsky
In reply to this post by Manish Goregaokar
On 2/27/18 5:28 PM, Manish Goregaokar wrote:

> You can already achieve this behavior with `rowspan=<large number>`

Only if you can guarantee that this number is in fact larger than the
number of rows in your rowgroup, yes?

And even then, is it exactly equivalent?

> and we should encourage developers to use Grid anyway

What does that have to do with anything?  This feature is for semantic
tables where you want a cell (e.g. one labeling something about an
entire rowgroup) to span to the end of the rowgroup.

> it's questionable whether it's used
> enough on the Web for it to be something we must keep for compat reasons.

Have we tried doing actual telemetry here?

-Boris
_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: Intent to unship: rowspan=0

Manish Goregaokar
> Have we tried doing actual telemetry here?

No, though we could. I'm skeptical given that no other browser implemented
it.

> What does that have to do with anything?

Given that we're the only browser implementing it until chrome (and likely
webkit?) ships it in a few months, it's as if it is a new feature for the
web, hence the suggestion to use Grid.


-Manish Goregaokar

On Tue, Feb 27, 2018 at 8:18 PM, Boris Zbarsky <[hidden email]> wrote:

> On 2/27/18 5:28 PM, Manish Goregaokar wrote:
>
> You can already achieve this behavior with `rowspan=<large number>`
>>
>
> Only if you can guarantee that this number is in fact larger than the
> number of rows in your rowgroup, yes?
>
> And even then, is it exactly equivalent?
>
> and we should encourage developers to use Grid anyway
>>
>
> What does that have to do with anything?  This feature is for semantic
> tables where you want a cell (e.g. one labeling something about an entire
> rowgroup) to span to the end of the rowgroup.
>
> it's questionable whether it's used
>> enough on the Web for it to be something we must keep for compat reasons.
>>
>
> Have we tried doing actual telemetry here?
>
> -Boris
> _______________________________________________
> dev-tech-layout mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-tech-layout
>
_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: Intent to unship: rowspan=0

Boris Zbarsky
In reply to this post by Boris Zbarsky
On 2/27/18 11:22 PM, Manish Goregaokar wrote:
>> What does that have to do with anything?
>
> Given that we're the only browser implementing it until chrome (and likely
> webkit?) ships it in a few months, it's as if it is a new feature for the
> web, hence the suggestion to use Grid.

Please explain to me how one would do this with Grid and a semantic
table in a sane way.

-Boris
_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: Intent to unship: rowspan=0

Manish Goregaokar
Oh, you're asking for it to continue to work with semantic HTML? That won't
work, you'd need to create a new table with grid stuff.

In that case we probably shouldn't unship?

-Manish Goregaokar

On Tue, Feb 27, 2018 at 8:38 PM, Boris Zbarsky <[hidden email]> wrote:

> On 2/27/18 11:22 PM, Manish Goregaokar wrote:
>
>> What does that have to do with anything?
>>>
>>
>> Given that we're the only browser implementing it until chrome (and likely
>> webkit?) ships it in a few months, it's as if it is a new feature for the
>> web, hence the suggestion to use Grid.
>>
>
> Please explain to me how one would do this with Grid and a semantic table
> in a sane way.
>
>
> -Boris
> _______________________________________________
> dev-tech-layout mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-tech-layout
>
_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: Intent to unship: rowspan=0

Henri Sivonen-2
In reply to this post by Manish Goregaokar
On Wed, Feb 28, 2018 at 12:28 AM, Manish Goregaokar
<[hidden email]> wrote:
> You can already achieve this behavior with `rowspan=<large number>`,

In terms of letting HTML validation produce useful results, telling
authors to use a bogus large number is worse than having a special
value (zero). If you use 0 and the table makes sense that way,
validator.nu is OK with the document, but if you use a bogus large
number, validator.nu, correctly, complains.

(So validator.nu is a piece of software in addition to Gecko and
Presto that supports this HTML feature.)

--
Henri Sivonen
[hidden email]
https://hsivonen.fi/
_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: Intent to unship: rowspan=0

Boris Zbarsky
In reply to this post by Boris Zbarsky
On 2/28/18 2:02 AM, Manish Goregaokar wrote:
> Oh, you're asking for it to continue to work with semantic HTML?

I'm saying that this feature is there for actual data tables.  And that
the suggestion that Grid is a replacement is not actually helpful given
that.

> That won't work, you'd need to create a new table with grid stuff.

Seems to me that asking people to do this for an actual data table is
just as bad as asking people to use tables for layout.  ;)

> In that case we probably shouldn't unship?

The one thing I haven't seen so far is why we should unship, really.  Is
the only reason that no one else supports it?  (To be clear, this can
absolutely be a valid reason, especially if the other UAs have
explicitly said they will not add support or the feature causes some
other problems too, in terms of either implementation or the health of
the web.)

-Boris
_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: Intent to unship: rowspan=0

Manish Goregaokar
> Is the only reason that no one else supports it?

Yes. (which makes me suspect that nobody uses it)


However, as mentioned, Chrome *has* added support, it's not stable yet.


-Manish Goregaokar

On Wed, Feb 28, 2018 at 5:19 AM, Boris Zbarsky <[hidden email]> wrote:

> On 2/28/18 2:02 AM, Manish Goregaokar wrote:
>
>> Oh, you're asking for it to continue to work with semantic HTML?
>>
>
> I'm saying that this feature is there for actual data tables.  And that
> the suggestion that Grid is a replacement is not actually helpful given
> that.
>
> That won't work, you'd need to create a new table with grid stuff.
>>
>
> Seems to me that asking people to do this for an actual data table is just
> as bad as asking people to use tables for layout.  ;)
>
> In that case we probably shouldn't unship?
>>
>
> The one thing I haven't seen so far is why we should unship, really.  Is
> the only reason that no one else supports it?  (To be clear, this can
> absolutely be a valid reason, especially if the other UAs have explicitly
> said they will not add support or the feature causes some other problems
> too, in terms of either implementation or the health of the web.)
>
>
> -Boris
> _______________________________________________
> dev-tech-layout mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-tech-layout
>
_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: Intent to unship: rowspan=0

Manish Goregaokar
Looks like there's no compelling reason to unship.

Retracting.

-Manish Goregaokar

On Wed, Feb 28, 2018 at 9:25 AM, Manish Goregaokar <[hidden email]>
wrote:

> > Is the only reason that no one else supports it?
>
> Yes. (which makes me suspect that nobody uses it)
>
>
> However, as mentioned, Chrome *has* added support, it's not stable yet.
>
>
> -Manish Goregaokar
>
> On Wed, Feb 28, 2018 at 5:19 AM, Boris Zbarsky <[hidden email]> wrote:
>
>> On 2/28/18 2:02 AM, Manish Goregaokar wrote:
>>
>>> Oh, you're asking for it to continue to work with semantic HTML?
>>>
>>
>> I'm saying that this feature is there for actual data tables.  And that
>> the suggestion that Grid is a replacement is not actually helpful given
>> that.
>>
>> That won't work, you'd need to create a new table with grid stuff.
>>>
>>
>> Seems to me that asking people to do this for an actual data table is
>> just as bad as asking people to use tables for layout.  ;)
>>
>> In that case we probably shouldn't unship?
>>>
>>
>> The one thing I haven't seen so far is why we should unship, really.  Is
>> the only reason that no one else supports it?  (To be clear, this can
>> absolutely be a valid reason, especially if the other UAs have explicitly
>> said they will not add support or the feature causes some other problems
>> too, in terms of either implementation or the health of the web.)
>>
>>
>> -Boris
>> _______________________________________________
>> dev-tech-layout mailing list
>> [hidden email]
>> https://lists.mozilla.org/listinfo/dev-tech-layout
>>
>
>
_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: Intent to unship: rowspan=0

L. David Baron
I would consider the lack of support in other browsers, and the
extra complexity in our codebase as a reasonably compelling reason.
Also perhaps that we've already (long ago, I think) unshipped
support for colspan=0 for similar reasons.

Table height calculation is among the least interoperable
longstanding features of the Web, and I think anything we can do to
simplify it and to improve interoperability on what's left would be
a good thing.

(Has Chrome also added support for colspan=0?)

-David

On Friday 2018-03-02 07:49 -0800, Manish Goregaokar wrote:

> Looks like there's no compelling reason to unship.
>
> Retracting.
>
> -Manish Goregaokar
>
> On Wed, Feb 28, 2018 at 9:25 AM, Manish Goregaokar <[hidden email]>
> wrote:
>
> > > Is the only reason that no one else supports it?
> >
> > Yes. (which makes me suspect that nobody uses it)
> >
> >
> > However, as mentioned, Chrome *has* added support, it's not stable yet.
> >
> >
> > -Manish Goregaokar
> >
> > On Wed, Feb 28, 2018 at 5:19 AM, Boris Zbarsky <[hidden email]> wrote:
> >
> >> On 2/28/18 2:02 AM, Manish Goregaokar wrote:
> >>
> >>> Oh, you're asking for it to continue to work with semantic HTML?
> >>>
> >>
> >> I'm saying that this feature is there for actual data tables.  And that
> >> the suggestion that Grid is a replacement is not actually helpful given
> >> that.
> >>
> >> That won't work, you'd need to create a new table with grid stuff.
> >>>
> >>
> >> Seems to me that asking people to do this for an actual data table is
> >> just as bad as asking people to use tables for layout.  ;)
> >>
> >> In that case we probably shouldn't unship?
> >>>
> >>
> >> The one thing I haven't seen so far is why we should unship, really.  Is
> >> the only reason that no one else supports it?  (To be clear, this can
> >> absolutely be a valid reason, especially if the other UAs have explicitly
> >> said they will not add support or the feature causes some other problems
> >> too, in terms of either implementation or the health of the web.)
> >>
> >>
> >> -Boris
> >> _______________________________________________
> >> dev-tech-layout mailing list
> >> [hidden email]
> >> https://lists.mozilla.org/listinfo/dev-tech-layout
> >>
> >
> >
> _______________________________________________
> dev-tech-layout mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-tech-layout
--
𝄞   L. David Baron                         http://dbaron.org/   𝄂
𝄢   Mozilla                          https://www.mozilla.org/   𝄂
             Before I built a wall I'd ask to know
             What I was walling in or walling out,
             And to whom I was like to give offense.
               - Robert Frost, Mending Wall (1914)

_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout

signature.asc (817 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Intent to unship: rowspan=0

Manish Goregaokar
Chrome decided not to do colspan after seeing that we unshipped it.

२ मार्च, २०१८ ११:१३ म.पू. रोजी, "L. David Baron" <[hidden email]> ने
लिहिले:

> I would consider the lack of support in other browsers, and the
> extra complexity in our codebase as a reasonably compelling reason.
> Also perhaps that we've already (long ago, I think) unshipped
> support for colspan=0 for similar reasons.
>
> Table height calculation is among the least interoperable
> longstanding features of the Web, and I think anything we can do to
> simplify it and to improve interoperability on what's left would be
> a good thing.
>
> (Has Chrome also added support for colspan=0?)
>
> -David
>
> On Friday 2018-03-02 07:49 -0800, Manish Goregaokar wrote:
> > Looks like there's no compelling reason to unship.
> >
> > Retracting.
> >
> > -Manish Goregaokar
> >
> > On Wed, Feb 28, 2018 at 9:25 AM, Manish Goregaokar <
> [hidden email]>
> > wrote:
> >
> > > > Is the only reason that no one else supports it?
> > >
> > > Yes. (which makes me suspect that nobody uses it)
> > >
> > >
> > > However, as mentioned, Chrome *has* added support, it's not stable yet.
> > >
> > >
> > > -Manish Goregaokar
> > >
> > > On Wed, Feb 28, 2018 at 5:19 AM, Boris Zbarsky <[hidden email]>
> wrote:
> > >
> > >> On 2/28/18 2:02 AM, Manish Goregaokar wrote:
> > >>
> > >>> Oh, you're asking for it to continue to work with semantic HTML?
> > >>>
> > >>
> > >> I'm saying that this feature is there for actual data tables.  And
> that
> > >> the suggestion that Grid is a replacement is not actually helpful
> given
> > >> that.
> > >>
> > >> That won't work, you'd need to create a new table with grid stuff.
> > >>>
> > >>
> > >> Seems to me that asking people to do this for an actual data table is
> > >> just as bad as asking people to use tables for layout.  ;)
> > >>
> > >> In that case we probably shouldn't unship?
> > >>>
> > >>
> > >> The one thing I haven't seen so far is why we should unship, really.
> Is
> > >> the only reason that no one else supports it?  (To be clear, this can
> > >> absolutely be a valid reason, especially if the other UAs have
> explicitly
> > >> said they will not add support or the feature causes some other
> problems
> > >> too, in terms of either implementation or the health of the web.)
> > >>
> > >>
> > >> -Boris
> > >> _______________________________________________
> > >> dev-tech-layout mailing list
> > >> [hidden email]
> > >> https://lists.mozilla.org/listinfo/dev-tech-layout
> > >>
> > >
> > >
> > _______________________________________________
> > dev-tech-layout mailing list
> > [hidden email]
> > https://lists.mozilla.org/listinfo/dev-tech-layout
>
> --
> 𝄞   L. David Baron                         http://dbaron.org/   𝄂
> 𝄢   Mozilla                          https://www.mozilla.org/   𝄂
>              Before I built a wall I'd ask to know
>              What I was walling in or walling out,
>              And to whom I was like to give offense.
>                - Robert Frost, Mending Wall (1914)
>
_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout