« TAD Review in the San Antonio Express-News | Main | Happiness Is... »

January 28, 2007

Technical Request

Mac users of Firefox: For some reason the "White Castle = Not Hamburgers" single entry is causing Firefox 2.0 on my Mac to choke; the page comes in fine on all other browsers including Firefox 2.0 for the PC and Safari on the Mac. If you're on Mac and have Firefox 2.0, could you check to see if that entry also causes you problems? I want to know if it's just me (yes, I cleared my cache; that's the first thing I did). Aside from browser choking there seem to be no other issues; my Mac is fine otherwise, as is the browser.

If it does cause you to choke, close out your browser, fire up your browser again, and let me know (of course, you can also let me know if it doesn't cause you any problems -- both data are valuable). If the same problem is happening to other people, then I'll need to look at the entry to see what's causing the problem. Otherwise, I'll just chalk it up to my own personal browser weirdness.

Thanks.

Posted by john at January 28, 2007 06:59 PM

Trackback Pings

TrackBack URL for this entry:
http://www.scalzi.com/mt2/mt-tb.cgi/4394

Comments

G. Jules | January 28, 2007 07:16 PM

I'm on Firefox 2.0.0.1 on a Mac, and it's not making my computer choke. It's fine, and the whole page seems to be loading.

A. A. | January 28, 2007 07:21 PM

no problems

Jeff Hentosz | January 28, 2007 07:30 PM

Works here. Latest Firefox, OS X 10.4.8, seven-year-old G4.

David "The Longtime Lurker" | January 28, 2007 07:30 PM

I don't have a mac but i just finished OMW and wanted to say, top notch!

David

Matt McIrvin | January 28, 2007 07:31 PM

No trouble here either.

paul | January 28, 2007 07:37 PM

worked fine for me.

-et- | January 28, 2007 07:41 PM


Freud might feel vindicated to hear that you used the word "choke" when talking about the problem your Mac is having with White Castle products.

With a warped smile,
- Tom -

Pablo Defendini | January 28, 2007 07:43 PM

Just fine over here as well.

Nathan who helped make this year's Sundance winner-Yipee | January 28, 2007 07:44 PM

No problems here.

Maureen M McCarty | January 28, 2007 07:45 PM

Firefox 1.0.6 Mac OS X 10.3.9 on a 4 year old iMac, looks fine here but seeing the words "White Castle" caused *me* to choke. Yucky.

sam young | January 28, 2007 07:46 PM

firefox 2.0.0.1 on OSX 10.3.9
no chokin' here

mee | January 28, 2007 07:56 PM

choke-free.....

John Romkey | January 28, 2007 07:56 PM

No choking here, either (Firefox 2.0.0.1 on Intel OS X 10.4.8). A bit of flashing as CSS gets things in order, but after the page load completes, it's fine.

What do you mean by 'choking'?

Perhaps you have a Firefox extension which is unhappy with the page?

Chang, father of pangolins | January 28, 2007 07:56 PM

Fine on mine, in FF 2.sumthin. But I have issues alll the time with FF. Like my keyboard gets disabled by it, until I quit FF and restart it. Then things are fine. Why?

Kenneth | January 28, 2007 07:59 PM

fine here.

KevinQ | January 28, 2007 07:59 PM

Chang, I have that same problem sometime (keyboard dropping out), but I find that if I close that window, not the whole program, it works just fine if I open a new window.

Otherwise, the page in question works just fine in Firefox 2.0.0.1, on a PowerBook G4 with 10.4.8.

K

Chang, father of pangolins | January 28, 2007 08:00 PM

Thanks, KEvinQ! I'll give it a shot!

Cat Vincent | January 28, 2007 08:13 PM

Firefox 2.0.0.1, iMac G5, 10.4.8, no problems with the page at all.

Mark | January 28, 2007 08:19 PM

No problems here: Firefox 2.0.0.1, OS X 10.4.8, MacBook Pro.

Jeff Hentosz | January 28, 2007 08:34 PM

FWIW — and some will already know this, some not — a lot of app ailments are cured with a dose of "Repair Permissions" via Disk Utility, in the Utilities folder in your Applications folder. Quit everything, run the utility, select your hard drive (you may have other volumes listed), repair permissions, then log out and restart. If trouble persists, I can also recommend the third party app Cocktail, which does the same thing and more, industrial-strength.

Gari. N. Corp | January 28, 2007 08:45 PM

No problem here. IBook G4, 10.4.8, FF 2.0.0.1

Jacob | January 28, 2007 09:09 PM

Firefox 2.0.0.1 on Mac OS 10.4.8: worked fine for me.

Joe Hass | January 28, 2007 09:23 PM

OK: Firefox 2.0.0.1, Mac OS 10.4.8

Doug Miller | January 28, 2007 09:38 PM

No problems in either FF 2.0.0.1 or a recent nightly build of Camino, which uses same rendering engine.

Michael | January 28, 2007 10:03 PM

No problems with 2.0.0.1 on a MacBook Pro.

Christian | January 28, 2007 10:17 PM

Hi, I'm a Mac.

And I'm a PC.

PC: So, can you access the hamburger thread?

Mac: Nope, my OS chews the colon out of a dead warthog...

PC: Excellent! Now I'm going to prance down an old fashioned cobblestone lane wearing a frilly bonnet and nothing else.

Mac: Damn you PC!


[yes, this was a Jackson Pollock post - no explanation needed]

Turtle | January 28, 2007 10:57 PM

Fine here. Back to lurking. :-)

LovelyAngel | January 28, 2007 10:58 PM

The White Castle entry and all comments display perfectly fine on my two Macs running Firefox 2.0.0.1. One Mac is a dual G5 PowerMac running Mac OS 10.4.7; the other is a PowerBook G4 running Mac OS 10.4.8. Mac users of course are finicky about quality and are unlikely to rank White Castle slyders as qualitatively better than anything (although they may be fine comfort food for some folks).

~Amy

Sue | January 28, 2007 11:03 PM

I'm using FF 2.0.0.1 on OS 10.4.8 and it comes up just fine.



http://www.google.com/search?client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&channel=s&hl=en&q=White+Castle+%3D+Not+Hamburgers&btnG=Google+Search



btw -- I agree with your opinion too :>

Jennifer Ouellette | January 28, 2007 11:03 PM

No problems at all. Came up perfectly...

Dan Bailey | January 28, 2007 11:19 PM

Mac OS X 10.4.5, Firefox 2.0.0.1. Works fine.

Karl Cook | January 28, 2007 11:29 PM

No problems using FF2.0.0.1 on a Titanium PowerBook G4/550.
One trick that might help: open terminal and do a [sudo periodic daily weekly monthly].
Or, better yet, consider installing Applejack, a command line util that lets you clear out all the old cache files and other stuff that can gunk up [why, yes, that's the technical term] your system if it never gets to run its routine maintenance tasks. Applejack also checks for corrupted preferences files too. I find that restarting in single-user mode, by holding down CMD+S and running it gets my Mac running quite snappily again. Disclosure: just a satisfied user...

clvrmnky | January 29, 2007 12:05 AM

OS X 10.4.8, Firefox 2.0.0.1.

The "white castle" entry renders ok, but my handy page inspector tells me you have one error:

"missing ) after argument list"

004809.html, line 1543

Not sure how much this code is generated server-side, but the script contents in the following context seems to be causing the rendering engine some problems.

"document.write('For some reason, your ..."

Castiron | January 29, 2007 12:17 AM

It shows happily on mine, 2.0.0.1, OS 10.3.9.

Alphabeter | January 29, 2007 01:42 AM

I am not surprised by the number of Mac users on here.

Clean as a whistle here. Firefox 2.0.1, OS 10.4.8, shiny new MacBookPro.

Alphabeter | January 29, 2007 01:45 AM

I am not surprised by the number of Mac users on here.

Clean as a whistle here. Firefox 2.0.1, OS 10.4.8, shiny new MacBookPro.

It might be because there is a coding error and you, as the account owner, can see it because its trying to get your attention to fix it.

But I call my computer Ziggy. Presume accordingly.

Steve Leigh | January 29, 2007 07:40 AM

Firefox 2.0.0.1, Mac OS 10.4.8 -- no problems loading at all.

Ed Lemon | January 29, 2007 10:26 AM

Firefox 2.0.0.1 on Mac OS 10.4.8: worked fine for me on my iMac 24".

Branko Collin | January 29, 2007 11:13 AM

This is a known problem. Apparently it happens a lot to Mac-owning In-N-Out Burger-eaters, i.e. people with no discernable taste. What happens is that the browser rather kills itself than display the offending page. The Firefox developers are working hard at the problem, or rather, they would be if they could be bothered.

Justin | January 29, 2007 11:45 AM

Okee dokee here, Scalzi -- OSX 10.3.9, G4 laptop, Firefox 2.0.0.1

Ted Lemon | January 29, 2007 12:50 PM

The page renders fine for me on Firefox on an Intel Mac. Maybe the problem is specific to the PPC version?

Anyway, the reason your keyboard gets into trouble is that Javascript steals key bindings when you go to a page that has fancy javascript. Big offenders are YouTube, gmail, sites like that. Probably some bad piece of Javascript is getting attached to the page you have open. If you dismiss it, the problem should go away.

David S. | January 29, 2007 10:01 PM

Works fine for me - OS X 10.4.8, FF 2.0.0.1. I'm thinking you may have some weird extension causing you grief.

Jeff H. | January 30, 2007 06:46 PM

No problem here. Firefox 2.0.0.1 on a G3 running 10.3.9.

Interestingly though, Sue's posting above runs off into the background...

You might want to check your extensions. A few are known to not play nice with Firefox 2.x.

Herb S. | January 31, 2007 04:10 PM

No problems here with Firefox 2.0.0.1, OS X 10.4.8 and my MacBook Pro Core2Duo. Just FYI.

Patrick | February 2, 2007 12:14 AM

I use Firefox more than any other browser, but it's one of the most choke-prone browsers I've ever dealt with.

I fully expected it to lock up to the point that I'd have to "Force Quit." I can do that in my sleep now after having used Firefox for a few years.

But there were no problems here, either. Amazing!

Jose Cabanillas | February 3, 2007 12:08 PM

No problems here with the post. OS 1.0.4.8, Firefox 2.0.0.1, dual G5 machine.

You are dead on regards In n Out v White Castle, but you'd better leave Krystal out of this discussion, or them's fightin' words....... ;^)

Nah, Krystal's ain't real food neither.

Post a comment.

Comments are moderated to stop spam; if your comment goes into moderation, it may take a couple of hours to be released. Please read this for my comment moderation policies.
Preview will not show paragraph breaks. Trust me, they're there.
The proprietor generally responds to commenters in kind. If you're polite, he'll be polite. If you're a jackass, he'll be a jackass. If you are ignorant, he may correct you.
When in doubt, read the comment thread rules.




Remember Me?

(you may use HTML tags for style)