444842 - table cells with colspan bigger than 1000 are collapsed

Status: NEW

(Core :: Layout: Tables, defect)

Description

[Jordanes]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; it; rv:1.9) Gecko/2008061004 Firefox/3.0
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; it; rv:1.9) Gecko/2008061004 Firefox/3.0

If a cell has colspan > 1000, it is rendered like it had colspan 1. Even firebug says 'colspan="1"'.
I flagged this as a minor bug because i understand it is not common to work with a table so huge, but I actually need such a colspan. On Safari it works fine, and the w3c standard do not set any limit to colspan, so I think it IS a bug, actually.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.



As far as I know, this colspan limit exists also in FF2.

Comment 1

[Jesse Ruderman]

Attachment: testcase

Comment 2

[Jesse Ruderman]

http://hg.mozilla.org/mozilla-central/index.cgi/annotate/2dda8388dd0c/content/html/content/src/nsHTMLTableCellElement.cpp#l265

Can our data structures deal with larger colspans, or is the limit necessary given the current implementation?

Comment 3

[Jesse Ruderman]

Bug 443089 suggests to me that our data structures can't deal.  cf bug 348954.

Comment 4

[Bernd]

http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/content/html/content/src/nsHTMLTableCellElement.cpp&rev=1.112&mark=264,265#250
man that hgblame is so lame  with a normal blame one would easily see bug 141818 as the reference. ==> WONTFIX

Comment 5

[Jesse Ruderman]

The fact that Safari can handle it suggests to me that we might be able to handle it with a better data structure...

Comment 6

[Bernd]

I don't see any use case for this other than exploits.

Comment 7

[Jordanes]

indeed a human should not be able to use a table of more than 1000 columns, but I as the developer do not know on which tables the users will test my component. (the component has also a "transpose x and y axes" button - I stumbled upon this bug using that button on a table of 1100 rows. Not an impossible event I believe.)

Comment 8

[Martijn Wargers (dead)]

IE7 seems to do exactly the same as Mozilla here.

Comment 9

[Bernd]

;-) IE6 too, you know reverse engineer is my second name 

Comment 10

[Wishm4st3r]

I have the same problem.. in IE7 the my table look great.
I use infinit colspan...

Comment 11

[Jesse Ruderman]

If you're using infinite colspan (colspan="-1"), I think you're hitting a different bug (not this one).

Comment 12

[Wishm4st3r]

No.. infinity with php.. I'm calculate the right colspan of the table... normaly have more of 1000

(In reply to comment #11)
> If you're using infinite colspan (colspan="-1"), I think you're hitting a
> different bug (not this one).

Comment 13

[Bernd]

Attachment: ie7 rendering of the testcase

I have big difficulties to see that comments 10 and 12 are about this bug. Martijn also did see something different.

Comment 14

[u304681]

(I originally commented in the Bug 321474, but I noticed it was closed)

I am aware of the original Bug 141818 that is the cause for this. Yet, in a newer Bug 688405, a similar rowspan limitation was raised.

Chrome is fine with colspan > 1000.

Use case: Pivot table. And I think with the amount of data we have, this limitation will be hit more and more often.

Comment 15

[Richard Zembron]

This is by all means an annoying bug. Other browsers cope fine with this.

Tables are useful for so many things. I use them to display GANT tables/schedules and project plans. Using colspan I can very effectively place activities and their duration on a horizontal timescale, while using rows for parallell activities.

At least allowing 1920 or 2560 columns would make a worthwhile improvement for screen rendering of such tables.

Comment 16

[adrianopedro]

Alreayd in 2017 and the bug still remains!!!