Heya,

Alright, with the help of a lot of admins both here and submitting tickets, we've got the biggest remaining problems with the editor narrowed down to two things: custom CSS and custom Javascript.  There are other problems with certain browsers and operating systems, but the major ones include not being able to edit at all.

In order to get around it -- without requiring changes on the part of guild administrators -- I'm going to have the editor load in a dialog similar to the content editors.  This will pull it outside the scope of the parent page's custom CSS and/or javascript, so it'll be completely self-contained.  The change will go live sometime today or tonight.

If there is custom javascript on the page that interferes with the dialog itself loading (which we've run across with content editors, member admin, etc.), it'll catch the error and load it via a standard window.open script.  The same error trapping and alternative loading will be applied to content editor windows, member admin, and anything else that loads in the dialogs.

Another thing going live tonight is a fix for content editors sometimes not showing the most up-to-date edit on submit, such as the welcome message editor.

It looks pretty interesting Aaron. I'll see how it functions on the Mac and report any bugs I catch. Thanks.