Mozdev.org

Last week I had hoped to get edit-in-place to a point where it was usable more globally (that is, it was a feature that could be enabled per-project and work on all pages). I was able to get it in place, but it took me a little longer than anticipated and I managed to find a couple more pieces that need nailed down before it's ready to test.

This coming week I'd like to get edit-in-place polished up a little more; this includes making sure that editing one piece of a page doesn't cause all other pieces on the page to be saved (ie, editing the main content shouldn't cause the navigation to be saved), creating actions for uploading images and creating new pages, and following up with the mozile PO to see if actions can be ironed out for Firefox 3.

• bug#20466 - WYSIWYG editing - Asked mozile dev why some actions seem broken; he said he'll try to look into it. Moved edit-in-place features so they work site-wide; ran into problems because it wasn't clear to me that the same origin policy doesn't apply to XMLHttpRequest (that is, I can't set document.domain to use XHR to access a parent domain). I researched some methods for working around this (after lots of research trying to figure out what was going on) but managed to get all javascript libaries and PHP code for saving changes installed in locations so that they appear to be coming from the current project's website.
• Javascript library updates - While working on bug#20466 I needed to update and reorganize the javascript libraries we use for site features
• bug#20789 - fixed bug with unreleasing a file