What specifically is wrong with Apple's JavaScript implementation? Did you file a bug? It's open source, so you can even go fix the bug yourself!

Ditto, Mike! Can we get more details on what exactly is wrong with Safari's JavaScript implementation? It'd be cool to get this solved once and for all....

Mike, we have our own bugs to deal with. What are you doing right now? ;-)

From what I understand there is no way in Javascript in Safari to place the cursor at a particular point within a textarea, but I could be wrong.

My engineers (who are some of the best at Javascript) say it's not possible. I trust them.

Thank you! I was having all kinds of bugginess after installing b3 and then b4. My quicklinks quit working, my posts would save but give a 500 error and no trackback, my blogroll plugin was giving me a template error.

All work now with this install.

Todd

PS:

Can anyone point me to a resource that helps get my trackbacks 'unblocked' from certain blogs? I've not been a troll to anyone and have tracked few sites (such as this blog) and gotten no permission errors.

This explains so much with MTlink. Here I thought it was me...

It's good! For some reason, I couldn't get the cron jobs working on b4. After the upgrade, it was back to normal.

I know that bug. I logged it quite a while ago. It is an annoying one.

I might see what I can do to fix it, but whether it actually makes it in to JavaScriptCore is a different question.

Jay, there is no spec'd way of placing the cursor in a textarea, period. There are methods in Mozilla and MSIE to do it, but they are both nonstandard extensions and are implemented differently.

Adding the functionality will require convincing Apple to add a nonstandard extension. I'm on it though.

Yesterday, I upgraded to Beta-5. The upgrade process was great. Everything is great. Thanks!

..is this looking like being the last beta release (including nightlies)?

I already said this on my blog, but just to let you know, my upgrade took all of 2 seconds after uploading the files. In fact, I'd be willing to wager it was less then 2 seconds.

Oh, and no bugs that I could come across.

I am going to do a clean out of MT from my server this weekend and do a full install, then see what I get for bugs.

I don't know if this is the right place to ask this question, slap me gentle if it's not, okay?

I upgraded to beta 5 this morning (flawless, as usual) and now I want to finish customizing the last few temmplates before I consider the heavy lifting done on my site. Yeah, there will be the release version but I don't expect to have major work to do.

My question is regarding the search template. I know it's at search_templates/default.tmpl. I understand that it had to be edited separately because it's a single template that works across all blogs so it couldn't be in the blog-specific "templates" area. But now with 3.2, that's no longer the case. Why didn't you bring it into the Movable Type interface now that you have system-wide settings? When I change my blog design, I have to remember to edit that template. Plus, I prefer linking my templates to files and that's not possible with the search template. Just a thought.

Another smooth upgrade!

Why didn't you bring it into the Movable Type interface now that you have system-wide settings?

Umm, because we had enough to do? Seriously, the search functionality needs a heck of a lot more love than just bringing the templates into the interface. And besides, you notice that there is no system-wide templates? When they come, they'll be done right.

We always have to balance the desire to improve something a little bit and doing it right. We did a lot in this release. To answer the question "Why didn't you do X", the answer is always going to be a mix of time, resources and priorities.

You did the right thing by issuing Beta 5. If you have to, issue Beta 6 and 7 and...

Admittedly, this is a roman a clef, as I'm in the same boat myself, managing a significant migration and system change for a big website. We had to delay launch... and delay it again... and again... and again. It's hard when you want to "be there" but you know you aren't ready to launch. It's great to see you opening up the beta process this way, and I'd participate myself if I could stomach any more beta testing in my life right now. :-)

Good luck! Break a leg!

Previous betas were running pretty slowly on my test server with a BerkeleyDB for some reason, but beta-5 is running incredibly fast. I don't know if it's something you've changed or if my host's suddenly upgraded the server, but I'm very impressed!

First of all - very smooth so far. I've tested since beta 3 and have moved the installation from a cPanel server to a Windows IIS 6 install without any issues whatsoever right up to this bet. Very clean, very smooth. Fantastic!

However, I notice the lack of these new design templates that's been mentioned. Can we try these out before the release? Are they presented in 3.2 as they would be in TypePad (i.e. graphical interface, pick 'n' choose) or is it simply a case of cutting and pasting from the Moveable Type web site?

We will release them with 3.2. The default templates are compatible with all of the new styles. Hang tight just for a couple days and you'll see what we have planned.

From Apple:

The latest WebKit sources (not yet in a released build) include support for selectionStart, selectionEnd, and setSelectionRange on text areas and text fields. I believe setSelectionRange will set the insertion point too if you give it a collapsed range.

So it should make it into the next release, hopefully that will be soon!

I tested the latest build of WebKit (Safari's engine) and it is in fact in there. So if you guys could disable it only for the current version of Safari and below, that will enable the functionality when it appears in the next Safari release.