P
pinson.nick
I've been playing around with dynamic tables for the last couple days
and have run into some interesting issues. I know how to work around
this issue, but was wondering if anyone had any insight as to why it's
happening in the first place:
I create table row and cell elements using a JS node creator and
append them to the table element. Cell attributes are set using JS as
well (setAttribute() method on the cell element objects). All is well
in Safari, but Firefox seems to get severely confused -- it doesn't
honor the rowspan attributes for the dynamically created cells that
contain them. Oddly, however, if I copy the generated HTML to a static
file, it renders fine.
You can see the results/differences in the following two files:
http://tiger3k.com/nick/project/flatten_new.html
http://tiger3k.com/nick/project/tabletest.html
I've tried appending the second row (the one without the rowspan)
first, and inserting the first row before it, with the same result. It
would appear firefox doesn't honor rowspan for dynamically created
table elements? Which seems odd -- it handles colspan with no issues.
and have run into some interesting issues. I know how to work around
this issue, but was wondering if anyone had any insight as to why it's
happening in the first place:
I create table row and cell elements using a JS node creator and
append them to the table element. Cell attributes are set using JS as
well (setAttribute() method on the cell element objects). All is well
in Safari, but Firefox seems to get severely confused -- it doesn't
honor the rowspan attributes for the dynamically created cells that
contain them. Oddly, however, if I copy the generated HTML to a static
file, it renders fine.
You can see the results/differences in the following two files:
http://tiger3k.com/nick/project/flatten_new.html
http://tiger3k.com/nick/project/tabletest.html
I've tried appending the second row (the one without the rowspan)
first, and inserting the first row before it, with the same result. It
would appear firefox doesn't honor rowspan for dynamically created
table elements? Which seems odd -- it handles colspan with no issues.