What did WordPress do with Firefox’s Spell Check?

I upgraded to WordPress 2.1.1 last night, and now WordPress wants me to use its spell checker instead of Firefox‘s.

This is really annoying as I don’t really want or need a new spell checker. Firefox’s works great. WordPress’s is just slow and laggy because it uses AJAX.

Also, the whole auto-save feature of WordPress would be nice if Firefox didn’t already have the Session Restore feature.

Its as if WordPress’s 2.1 roadmap consisted of reimplementing Firefox 2.0 features in AJAX…

I like WordPress alot, but these new features are just a nuisance.

Anyone know how to turn these features off?

Update: My friend Dan pointed out that someone has submitted a bug to WordPress for the Firefox spellcheck issue.

This entry was posted in Open Source, PHP, Technology. Bookmark the permalink.
  • http://dancoulter.com Dan Coulter

    This is a known bug. Someone posted it in the tracker today:
    http://trac.wordpress.org/ticket/3847

    I haven’t tested this, but I doubt that Firefox’s session restore works with WYSIWYG editors. Either way, it’s still nice for IE and Safari users.

  • http://dancoulter.com Dan Coulter

    And I just uploaded a patch that will fix that problem. If the powers that be see fit, it may even make it into WP 2.1.2. If you can’t wait, just add the appropriate line from the diff.

    http://trac.wordpress.org/attachment/ticket/3847/3847.diff

  • http://dancoulter.com Dan Coulter

    After re-reading that ticket, I realized that they were talking about the TinyMCE spellchecker, not the firefox one. As such, I’ve created a new ticket here:

    http://trac.wordpress.org/ticket/3856

  • http://dancoulter.com Dan Coulter

    Another comment from me!

    You’re probably safe, but you might want to check this out:
    http://wordpress.org/development/2007/03/upgrade-212/