Safari support
Scott Andrew LePera <[email protected]>
| Newsgroups | gmane.comp.web.mod-pubsub.devel |
|---|---|
| Message-ID | <[email protected]> |
So, I was able to turn on the debugging console in Safari (see
instructions below). I pointed Safari at BlogChatter, with the JS
connector debug flag, and there were no JS errors logged. That's good news!
The tunnel frame still turns blue in Safari indicating that the frame is
ready (and obviously frameset access is working). I'm guessing that, for
some reason, the tunnelLoadCallback isn't being invoked.
I haven't got much time to work on this during the weekend, but I
thought I'd mention it in case anyone has any ideas. We really need
BlogChatter to work on Safari if we want to impress OSX users.
To turn on the JS debugging in Safari (thanks to Darin Kadrioski for the
info):
1. Quit Safari if it's running.
2. Start the terminal (Applications -->Utilities --> Terminal).
3. Type the following and hit return:
defaults write com.apple.Safari IncludeDebugMenu 1
4. Close the terminal and restart Safari.
5. There is now a debug menu to the right of the help menu. Pull it down
and select "Log Javascript Exceptions"
6. Open the console (Applications --> Utilities --> Console).
JS errors should now be logged in the console.
scottandrew
--
Scott Andrew LePera
Scott Andrew and the Walkingbirds
Lo-fi DIY acoustic pop and weirdo country thing
[email protected]
http://www.scottandrew.com
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01