Re: Intent to unship: rowspan=0
On Wed, Feb 28, 2018 at 12:28 AM, Manish Goregaokarwrote: > You can already achieve this behavior with `rowspan=`, 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 hsivo...@hsivonen.fi https://hsivonen.fi/ ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Intent to unship: rowspan=0
On 2/27/18 5:28 PM, Manish Goregaokar wrote: You can already achieve this behavior with `rowspan=` 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-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Intent to unship: rowspan=0
(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 Goregaokarwrote: > 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=`, 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-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Intent to unship: rowspan=0
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=`, 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-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform