Matt on Not-WordPress

← New Feedback Cool Fade →

Safari Support

August 31, 2005 · 10 Comments

I just wanted to post a quick clarification that Safari is not quite up to snuff for all the things we’re doing yet on WordPress.com. Where possible we will try to make it as elegant an experience as we can, but the Webkit engine is still evolving pretty rapidly and it may be a release or two before it’s fully caught up with things like Firefox.

Categories: Wordpress.com
Tagged:

10 responses so far ↓

  • Jon // August 31, 2005 at 4:03 am

    I guess maybe what I’ll be asking is the obvious, but just for clarification, would you be thinking of/referring to the AJAX functions and/or the WYSIWYG box (in particular)? I’m just curious to ask. Sadly stuck with OS X 10.2, and Safari 1.0 as a result. :-\ Oh well, go Firefox!

  • Jon // August 31, 2005 at 4:04 am

    Oh and I like the new look. :)

  • Matt // August 31, 2005 at 4:07 am

    Don’t mind the theme, I’m switching it around to test out everything.

    Safari doesn’t (and can’t) support the WYSIWYG much at all, and there are a few AJAX things that we’re still debugging.

  • CarLBanks // August 31, 2005 at 3:31 pm

    This is one of the reasons I switched from Opera back to Firefox. 1.6 WYSIWYG was just too good to pass up.

  • Budi // August 31, 2005 at 4:37 pm

    I found this unsupported thing on safari when I was trying to send a feedback and there’s nothing happened. I couldn’t write anything. And then, when I switched into firefox everything was OK.

    Thanks for the information, Matt ;)

  • budi on wordpress.com // August 31, 2005 at 4:53 pm

    Safari Support

    I had a problem to send a feedback in the dashborad via Safari this morning, the AJAX seems not working at all. Today, Matt, better known as photomatt, has posted a clarification that Safari is not quite up to snuff for all the things they’re d…

  • ALT1040 » Weblog en WordPress.com // September 7, 2005 at 4:26 am

    [...] No puedo hacer alguna de las cosas básicas porque el AJAX usado en las páginas de administración del sitio no son compatibles con Safari [Matt habla más al respecto]. [...]

  • marlinespike // October 19, 2005 at 11:13 pm

    Are the issues with Safari documented anywhere? Those of us who use Safari can send Apple feedback or submit (consumer level) “bug reports”. People who are registered with Apple’s developer site can submit bug reports with real tracking numbers and everything.

    What else doesn’t work right? Giving them specific examples might make a difference.

  • Jim // November 18, 2005 at 8:45 pm

    Apple is clear on how little of Ajax’s “higher abilities” they support:

    http://developer.apple.com/internet/safari/faq.html

    Things I saw that made me jump:
    1) A quote: “XSLT not available via JavaScript for application to arbitrary XML in an HTML page.”

    2) : Does Safari support XMLHttpRequest objects?

    Yes again! - Safari 1.2’s implementation follows the Mozilla model and successfully runs the Mozilla examples at Mozilla.org EXCEPT for the those requiring DOMParser.

    Translation, Safari blows. Do you know alternatitives to these shortcomings? The workaround must be elaborate

  • Oskar Syahbana // January 9, 2006 at 10:55 pm

    Safari is developed using KHTML engine right? I think these browser (Kamelleon, Safari, etc) do have a problem on displaying wordpress editor, even on WYSIWYG editor turned off.

Leave a Comment