Linked by Thom Holwerda on Fri 7th Jan 2011 18:00 UTC
Thread beginning with comment 456809
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2006-07-14
For historical record keeping purposes, it "works" now because the comment that triggered the bug is no longer a "top Comment", So its not in the page and not triggering the odd firefox bug. So if Osnews "web editors" can't find the problem anymore, that's why.
In the future you can do one of two things to prevent this issue:
1) Remove double hyphens from comments displayed in the top comment section.
2) Remove the output of the top comments. Why are they there, but commented out? Tis Ghetto.