Skip to main content

Bug Tracker

Side navigation

#4586 closed bug (worksforme)

Opened April 23, 2009 06:09PM UTC

Closed October 09, 2010 02:05AM UTC

Last modified September 07, 2012 01:30PM UTC

jQuery causing table borders to dissapear in FF3

Reported by: anpsince83 Owned by:
Priority: minor Milestone: 1.4
Component: core Version: 1.3.2
Keywords: Cc:
Blocked by: Blocking:

I set up a test case for this here:

jQuery is causing tables with border-collapse: collapse, to lose their borders in FireFox 3 (3.0.9).

We have one main stylesheet that has our reset and global styles. In that we define table { border-collapse: collapse; }. We include this stylesheet, then jquery. After that we will include any view includes, in this case another stylesheet that defines the styles for a table with borders. In FF3 the borders disappear after jQuery initializes. In all other browsers the borders remain. Take jQuery out, the borders are back in FF3.

What's interesting is that if I define the table styles inline, the borders remain, or if I move the stylesheet that defines the table styles above where jQuery is included the borders remain.

This is easily worked around, but bizarre nonetheless.

Attachments (0)
Change History (3)

Changed June 12, 2010 06:33PM UTC by dmethvin comment:1

component: unfiledcore

Hmm, this is interesting because I think I have seen that myself. Your test case is gone though. Can you attach a copy of it or point to another location?

Changed October 09, 2010 02:05AM UTC by addyosmani comment:2

resolution: → worksforme
status: newclosed

Testing this out with FireFox 3 with jQuery 1.4.2 and 1.3.2, it appears that the border-collapse:collapse property is still being maintained even when jQuery is being loaded.

Given this and that the original test case is no longer available, I am closing this ticket as worksforme, however if the original ticket submitter would like to re-open a new ticket with further test cases I would be more than happy to check them out.

Changed September 07, 2012 01:30PM UTC by anonymous comment:3

Noticed the same in IE8 standards mode (IE7/FF15/quirks mode : no issue)