Sure, sure. Functionally, they’re completely different. However heck if I didn’t know concerning the wacky thresholds till Jens Oliver Meiert tooted a pair of fast polls.
In response to the HTML Customary:
- If the present cell has a
colspanattribute, then parse that attribute’s worth, and let colspan be the end result.
If parsing that worth failed, or returned zero, or if the attribute is absent, then let colspan be 1, as a substitute.
If colspan is larger than 1000, let or not it’s 1000 as a substitute.- If the present cell has a
rowspanattribute, then parse that attribute’s worth, and let rowspan be the end result.
If parsing that worth failed or if the attribute is absent, then let rowspan be 1, as a substitute.
If rowspan is larger than 65534, let or not it’s 65534 as a substitute.
I noticed the solutions prematurely and know I’d have flubbed rowspan. Apparently, 1000 desk columns are loads of columns to span without delay, whereas 65534 is the magic quantity for clamping what number of rows we are able to span at a time. Why is the candy spot for rowspan 6,4543 spans better than colspan? There are often good causes for these items.
What that purpose is, darned if I do know, however now I’ve a bit of nugget for cocktail chatter in my again pocket.
How are the `colspan` and `rowspan` attributes completely different? initially printed on CSS-Methods, which is a part of the DigitalOcean household. You need to get the e-newsletter.
