Re: Intent to unship: rowspan=0

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 <[email protected]>
> 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
> [email protected]
> https://lists.mozilla.org/listinfo/dev-tech-layout
>