Bug in the Forum

from Sins Forums
This one has been bugging me since you first opened the beat up to us: The "Beta summary" stickied thread looks to have some broken HTML or something in it. When viewing in a FireFox browser, I can only see about the first 1/3rd of the entries; it seems to cut off at one particular line. If I "view source" or turn off CSS styling I can see the rest in plain-text unformatted goodness, but I think someone's got to close an open tag or something in there. Let me know and I'll fire off a screenshot.
4,148 views 14 replies
Reply #1 from Sins Forums Top
Its a known bug with the forum code + firefox -- you can either use I. E. or the link at the top of the thread to an off-site copy of the thread.
Reply #2 from Sins Forums Top
what does this have to do with the beta???
CursorFX - Customize your Windows cursor
Reply #3 from Sins Forums Top

what does this have to do with the beta???


It makes the beta feedback thread, well, useless.
Reply #4 from Sins Forums Top

what does this have to do with the beta???


lol, positive as always
Reply #5 from Sins Forums Top
I missed the edit-change to the first post that gave the alternate link. Woops!
Reply #6 from Sins Forums Top

what does this have to do with the beta???


Guilt by association?
Reply #7 from Sins Forums Top
LOL!

Anyone tried validating that page? No wonder Firefox can't show it! 900 errors! W3C Validator Results...

That's 900 versus some 89 separate errors on a normal forum page. Browsers are only so much error tolerant, and IE thinks it is the only correct way to make websites, so no surprise there. Don'tcha just love ASP?

The error appears to be a maximum size restriction, which is testable if you ctrl+scrollwheel to resize the text. Resize it up and down and the page size doesn't change, just where the text gets clipped. Don't know what exact error is killing it, but then again you aren't paying me.
Reply #8 from Sins Forums Top
It's a bug in firefox (#215055 in Bugzilla). It's been assigned to someone to fix for four years, with no resolution as yet. *sigh*
Reply #9 from Sins Forums Top
Best out of 5 maybe?
Reply #10 from Sins Forums Top
Well, no resolution but by my testing only testcase 3 failed, and that was approximately twice as better as reported when the testcase was written. (1600+ rather than 819) You don't need to change the overflow setting or set it at all with the way your layout is designed though, so that is basically aggravating the problem. I'll test it out with FF3 and see if there's any improvement...

Your block probably would render better if you removed the overflow-y line.
Code: css
  1. .Body_Outter_Region {index.aspx (line 81)
  2. height:auto;
  3. margin-left:110px;
  4. overflow-x:hidden;
  5. /* overflow-y:auto; */
  6. width:790px;
  7. }
Reply #11 from Sins Forums Top
Well, no resolution but by my testing only testcase 3 failed, and that was approximately twice as better as reported when the testcase was written.


The fourth also fails. And simply improving it from failing at 14bits long to failing at 15bits isn't much of a fix at all.

Removing the overflow-y line makes no difference; the bug equally affects it with no overflow setting explicitly declared.

Granted, the forum html is a mess, but this is definitely a firefox bug. The web guys have looked into it but to work around it would basically require the entire layout to be redone again. Not exactly a fast or cheap thing to do.

I've already tried it in Minefield (FF3a8), and it fails even more spectacularly (the background stops painting before it even gets as far as 32768px).
Reply #12 from Sins Forums Top
Agreed. Haha, maybe pagination by page length?

I tried Gran Paradiso (3 Alpha 7) and it seems to have taken a step backwards in the Alpha. Hopefully they'll get this sort of thing fixed.
Reply #13 from Sins Forums Top
At least from beating on it all morning I found a 'quick' way to get around it. It's not pretty, but it makes page 1 of the thread readable in firefox.
Reply #14 from Sins Forums Top

At least from beating on it all morning I found a 'quick' way to get around it. It's not pretty, but it makes page 1 of the thread readable in firefox.



O.o cool!