Is it just me, or does the site have a problem?

13 Comments

1. 

   wolverine writer on March 17, 2005 at 4:28 am

   All good here, everyday since launch and today.

2. 

   Athenian on March 17, 2005 at 7:19 am

   Using Mac OS X and Safari, site is working fine.

3. 

   xxxxxxx on March 17, 2005 at 7:39 am

   Try exiting Firefox and restarting. If that doesn’t cure the problem, try clearing your cache. A buggy script embedded in a blogad is probably messing things up for you.

   I use adblock, so the ads don’t load for me and I don’t have to worry about that stuff (makes all sites a lot faster, too). Firefox on XP here too, BTW.

4. 

   BooMan on March 17, 2005 at 9:53 am

   ‘Andyschm’ or ‘Andy’ is my programmer.  And between the 3 of us we’ll figure it out.  Browser stuff is not my area of expertise.  But I’ll make sure we find out what’s up.

5. 

   2care4others on March 17, 2005 at 10:24 am

   I’ve had this problem also, but I’ve found out how to get around it.

   Click the back button and it works.

   When I normally go into a front page and it doesn’t do what you described above, the first page I see is just blog ads, but the rest of the site is down below. I think it has to do with the size of my monitor (17 inch, I’m still back in the stone age). But if I scroll down lower, the site is there.

   I have actually had the situation you’ve described also happen on Kos though. I agree with Boo that it’s a bad script in a blogad.

   Try the back button, I’ve seemed to get around the situation that way (and I’m on Firefox too).

6. 

   andy on March 17, 2005 at 1:18 pm

   Testing with Firefox+Windows XP here, I don’t see any problem.  Are you running the latest version?  Any unusual extentsions enabled?  Right-click on the page and select “Page Info” from the context menu….  anything unusual there, what does it say under ‘Rendering Mode’?

   • 

     andy on March 17, 2005 at 1:26 pm

     nevermind…  see my next comment.

7. 

   andy on March 17, 2005 at 1:26 pm

   I am subscribed to the Scoop-bugs mailing list and this came up today; it may be revelant.  (summary: set Rate Comments = No in your comment preferences)

   http://bugz.mostly-harmless.ca/show_bug.cgi?id=177

              Summary: Display of long threads freezes browser
              Product: Scoop
              Version: cvs-STABLE
             Platform: All
           OS/Version: other
               Status: NEW
             Severity: normal
             Priority: P2
            Component: HTML output
           AssignedTo: janra@write-on.org
           ReportedBy: robertdfeinman@netscape.net
            QAContact: Scoop-bugs@lists.kuro5hin.org

   Several people have complained on forums run by Scoop (mydd, dailykos, for
   example) that when trying to display a long thread the display freezes.
   The screen starts to display, then goes blank, the browser stays busy. If you
   press the stop and then hit return in the URL field the screen usually paints
   properly.
   This seems to be an issue with Firefox 1.0 and latest Mozilla builds.
   It may be a browser issue, but seems only to happen with scoop generated pages,
   so it a minimum you might want to explore why.

   Response:

   This problem has been around forever, and it’s only a Scoop issue tangentially.
   The problem is that a lot of browsers have terrible memory management on form
   widgets. So when you have comment rating enabled, and a very long thread, the
   page will include a lot of selectboxes for ratings. Certain browser and platform
   combinations have choked on this. When I’ve seen reports of this, I usually tell
   people to try disabling ratings and that suually fixes it, confirming the form
   widgets diagnosis.

   So it’s a Scoop problem in that we’re generating these forms, and adding some
   other way to do ratings would be helpful. We’ve talked about doing it with
   javascript, the way Netflix does their movie ratings. And it’s also not a Scoop
   problem in that the browser freezing is due to buggy browsers.

   So I guess the answer is that we know about the problem, and know what causes it
   and how to work around it, and a fix for those who need one should be
   forthcoming eventually. But also I don’t tihnk it’s very high on anyone’s
   priority list, so I can’t say when that fix is likely to appear.

   • 

     canberra boy on March 17, 2005 at 6:20 pm

     This does seem to fix the problem, although of course I lose the ability to rate comments.  Think I’ll just put up with it and use the back button on the browser.

     Clearing the cache unfortunately didn’t help.

     Thanks everyone for suggestions.

     • 

       pyrrho on March 17, 2005 at 6:40 pm

       hmmm, maybe that’s it… but check out my fix too, I know my fix is a problem at slashdot.

8. 

   pyrrho on March 17, 2005 at 6:38 pm

   I bet I know the problem.  Firefox/Mozilla have a problem with some elements of pages that load after… basically it can set up the table sizes before it loads the elements in it.

   if this is it… you can fix it by, after the page is done loading… hold down control and press “+” then “-“.

   This works because ctrl-+ will increase the font size (actually kind of good to know) and ctrl-“-” reduces it… hitting both leaves the font size the same in the end but has told the browser to recalculate all the table widths, since you already have all the bits, they get calculated correctly.

   • 

     canberra boy on March 17, 2005 at 6:59 pm

     Thanks for the idea, but it didn’t work for me.  I’m pretty convinced it’s the Scoop bug that Andy mentioned.

     • 

       pyrrho on March 17, 2005 at 7:55 pm

       at least you have it figured.