MF hanging Safari

April 14, 2003 7:22 AM

Has anyone noticed a problem with MF and Safari >=0.67? These are the builds with tabs; 0.73, the first public release, went into open beta today. I often find that the MF home page will hang Safari until it's done (spinning cursor, can't scroll, can't leave the page early, no interaction at all.) This doesn't seem to happen with the lofi page (or anywhere else).
posted by Armitage Shanks to Bugs at 7:22 AM (21 comments total)

At home, I've used the secret .67 build since it leaked onto the net and I've used all of the previous public Safari builds and I've never had a problem with MetaFilter hanging my screen. I'm having a problem with Blogshares, but never MeFi. Using 10.2.4 and 10.2.5
posted by mkelley at 8:34 AM on April 14, 2003

Using Safari v73 with 10.2.5, finding that the menu text on the blue isn't styled properly. Fine on MeTa.

Momentary spinning wheel while the Google TextAd loaded on the front page just now; no delay noticed when I checked earlier.
posted by mcwetboy at 8:45 AM on April 14, 2003

If your browser has a "b" on the end of its version number, blahblahblah.

That said, shouldn't you be complaining about this to Apple instead?
posted by Su at 9:14 AM on April 14, 2003

That said, shouldn't you be complaining about this to Apple instead?

Not if it only happens to one person on one site. Hence the question.
posted by Armitage Shanks at 9:19 AM on April 14, 2003

I've had no problems accessing MetaFilter with any of the Safari builds, offical or not. Currently using the Beta 2 (v73), OS X 10.2.5
posted by jazon at 9:54 AM on April 14, 2003

Su, what the hell is your problem?
posted by eilatan at 10:18 AM on April 14, 2003

Thanks everyone for the feedback, obviously a problem at my end.
posted by Armitage Shanks at 10:43 AM on April 14, 2003

google ads.
posted by crunchland at 11:29 AM on April 14, 2003

Silly Mac users, why not try a real computer? I can build you one for about the price of MS Office on teh Mac!

*runs*

/loving mac os x more every day but can't help smile at silly PC users' jealousy.
posted by Space Coyote at 11:53 AM on April 14, 2003

For what it's worth, I'm using Safari 1.0b v60, OS 10.2.5, and have had no problems w/ anything Meta...
posted by herc at 11:57 AM on April 14, 2003

Su's completely right. If Matt decides it's a good idea to start tweaking MeFi for every browser still in beta with a .002% market share, then he obviously smokes a lot more hash than I give him credit for. Yes, I use Safari, yes, I love it, and yeah, it eats CSS for lunch and murders entire websites. Isn't that the fun of being an early adopter?
posted by RJ Reynolds at 11:58 AM on April 14, 2003

Crunchland: You're absolutely right, it is the text ad causing the delay.

RJ: Su's point seems utterly obvious and completely unhelpful to me. I *know* it's a beta release. Before I'd "complain to Apple" or start digging around my setup, it makes sense to check if the problem only occurs with my browser on my machine. The only way to find that out is to ask. I'm not asking anyone to tweak anything on my behalf.
posted by Armitage Shanks at 12:36 PM on April 14, 2003

'Kay.
posted by RJ Reynolds at 2:04 PM on April 14, 2003

The google ads are in an IFRAME, so I suspect Safari is still working on support for that infrequently used bit of markup.
posted by mathowie (staff) at 2:44 PM on April 14, 2003

Armitage Shanks has the right of it. No point in complaining to Apple about something if it's only a local problem.

At any rate, I don't see why Su has to make that comment in every single thread that mentions a Safari rendering issue. I don't see Su telling folks to get Opera or Mozilla or whatever the hell the best PC browser is when someone notices something not displaying properly in IE.
posted by eilatan at 3:45 PM on April 14, 2003

The point is that Safari is still beta which be definition means that you should expect these kinds of issues when "testing" it. It's for the browser to fix, not the site designer.
posted by willnot at 4:20 PM on April 14, 2003

It's for the browser to fix, not the site designer.

Nobody has suggested that the site designer should do anything.
Nobody has suggested that the site designer should do anything.
Nobody has suggested that the site designer should do anything.
Nobody has suggested that the site designer should do anything.
Nobody has suggested that the site designer should do anything.
Thank you and good night.
posted by Armitage Shanks at 4:43 PM on April 14, 2003

Listen, will you please stop begging for the site designer to do something? I'm so sick of you!
posted by RJ Reynolds at 8:05 PM on April 14, 2003

I don't see Su telling folks to get Opera or Mozilla or whatever the hell the best PC browser is when someone notices something not displaying properly in IE.

That is an entirely different issue, and you know it, or should, anyway. Those browsers are at full, public release for that matter, versions. Safari is under such heavy development that one of the people behind it can maintain a blog on that topic alone. It is not complete. Weirdness goes to the software, not web, developers. Apple is aware of this; they built a button into the interface for it. If there is nothing wrong with the page^*, then the browser is to blame. There are several reasons for nobody to be doing anything special whatsoever for Safari at this time. Case in point: Just about every Safari-affecting CSS hack that was found only a few months ago was fixed with today's release, ie: stuff that someone might have done to fix things for it, now likely break things for it.

I don't care what program anybody uses, as long as they can browse around as they see fit, so no, I'm not going to harp about how much I hate Opera. On the other hand, this is not the place to winge about how much an admittedly incomplete piece of software is misbehaving. Further, Armitage seems to be under the potentially incorrect impression that since no one else(of a whole three total responses) had the problem s/he did, then it must not be a problem. Because, you know...everybody's systems act and are configured the same way, and OSX doesn't demonstrate any random strange behavior.

At any rate, I don't see why Su has to make that comment in every single thread that mentions a Safari rendering issue.

Safari itself it not the issue at all. It just happens to be the only beta of any significance at the moment. If you search further back, you'll find me saying the same things about pre-final Mozilla, which has never been as perfect as its zealots would have liked the world to think.

But on to the real issue: You have yet to provide a reason for what I say being wrong. Instead, you're just complaining about the fact that I'm saying it. So is it that you'd prefer it be different people saying it?

^* The MeFi front page will likely never quite validate, for a few reasons, but there is rarely anything wrong with it that should cause any browser significant difficulty.
posted by Su at 9:24 PM on April 14, 2003

Christ, what a condescending load of drivel. So much free time and apparently so little to do.

If anyone else should run into this problem, redirecting pagead.googlesyndication.com to 127.0.0.1 made it go away for me.
posted by Armitage Shanks at 5:34 AM on April 15, 2003

Christ, what a condescending load of drivel.

Oh. Well that settles it, then, doesn't it?
posted by Su at 9:46 AM on April 15, 2003