A year ago today, I wrote about how WordPress (version 2.2.3 at the time) and the Safari browser (version 3.0.3) didn't play nice together.
Well, they do now.
I'm not sure when it happened. But somewhere along the way, either Safari or WordPress ... or both ... changed something.
I'm running WordPress 2.6.2 now, and Safari 3.1.2 (5525.20.1). And, unlike last September 25th, I'm able to write a post on WordPress, using Safari, and everything's just fine.
Whether I use the HTML mode (which I do use most often) or the Visual mode (which is sometimes really handy), everything is now fine.
I wonder if WordPress knows. You see, the topic is one of the items listed as "Under Consideration" for a WordPress enhancement.
And it works with both Mac and Windows (Safari 3.1.2 / 525.21). I wrote this on my Mac, part using OS X 10.5.5 and part using Windows XP SP3.
So, whatever problems there were ... are resolved.
At least for me. At least for now.
Showing posts with label Safari. Show all posts
Showing posts with label Safari. Show all posts
Thursday, September 25, 2008
Tuesday, September 25, 2007
Problems with Safari browser and WordPress
See update.
¶ If this post is hard to read, it's because I'm using the Safari browser to write this on a WordPress blog. ¶ You see, I got a MacBook computer recently. And I've been trying out all the functions of a Mac as I make the change from 20+ years of PC computing. ¶ Now, to be sure, I do like the MacBook. I like it a lot. Oh, sure, there are some differences. But the main thing is, the MacBook is easy to use. Really easy to use. ¶ But it's not perfect. ¶ You see, Apple has their own browser: Safari. ¶ It's a fine browser, to be sure. It's pretty fast. Everything on the Mac is fast. Except for my Microsoft Office 2004 suite. ¶ So, Safari is fast. But it has a bug with WordPress. ¶ Now, if you don't use WordPress, you might be just fine. But WordPress and Safari don't play nice together. ¶ It seems that if you use the Visual Editor for writing ... and I do ... the paragraph formatting screws up. ¶ How bad? Well, you see those little paragraph marks all through this post? That's where I put paragraphs when I wrote this. ¶ And, you see how this has all run together as one big paragraph? That's because of the bug in Safari. ¶ Now, there are reports that the new version of Safari has solved this issue. ¶ But it hasn't. ¶ You see, I'm using Safari 3.0.3 (522.12.1) ... and WordPress 2.2.3. ¶ Yes, that's a beta version. But it's the version that they say has the issue fixed. And it doesn't. ¶ So, excuse how this post looks. But it looks this way because Safari 3 hasn't fixed the bug. ¶ Which means I'll continue using Firefox. Which I like. And won't be using Safari. Which I thought I'd like ... and would if Apple would get off their butts and get it fixed.
UPDATE: Some time in the past year, things got better. They play nice now. Read about it here.
¶ If this post is hard to read, it's because I'm using the Safari browser to write this on a WordPress blog. ¶ You see, I got a MacBook computer recently. And I've been trying out all the functions of a Mac as I make the change from 20+ years of PC computing. ¶ Now, to be sure, I do like the MacBook. I like it a lot. Oh, sure, there are some differences. But the main thing is, the MacBook is easy to use. Really easy to use. ¶ But it's not perfect. ¶ You see, Apple has their own browser: Safari. ¶ It's a fine browser, to be sure. It's pretty fast. Everything on the Mac is fast. Except for my Microsoft Office 2004 suite. ¶ So, Safari is fast. But it has a bug with WordPress. ¶ Now, if you don't use WordPress, you might be just fine. But WordPress and Safari don't play nice together. ¶ It seems that if you use the Visual Editor for writing ... and I do ... the paragraph formatting screws up. ¶ How bad? Well, you see those little paragraph marks all through this post? That's where I put paragraphs when I wrote this. ¶ And, you see how this has all run together as one big paragraph? That's because of the bug in Safari. ¶ Now, there are reports that the new version of Safari has solved this issue. ¶ But it hasn't. ¶ You see, I'm using Safari 3.0.3 (522.12.1) ... and WordPress 2.2.3. ¶ Yes, that's a beta version. But it's the version that they say has the issue fixed. And it doesn't. ¶ So, excuse how this post looks. But it looks this way because Safari 3 hasn't fixed the bug. ¶ Which means I'll continue using Firefox. Which I like. And won't be using Safari. Which I thought I'd like ... and would if Apple would get off their butts and get it fixed.
UPDATE: Some time in the past year, things got better. They play nice now. Read about it here.
Subscribe to:
Posts (Atom)