After downloading the latest build, things are much better; resizing text seems to be the only thing not yet working.

Also, text alignment doesn't seem to work.

Can we get this put on the "Compatibility Hit List"? Other issues I see: No way to move images which are inserted using cut and paste. Using Firefox you can drag the images within the text.

Did some investigation and found these two errors in the java script console. Probrably going to be more but this might get an investigation started?? I noted the error and the code snipit it occured in. The <<<< desigates the line where the error occured. ERROR #1: Null Value Error this.savedSelection = selection.getRangeAt(0).cloneRange(); saveSelection:function(){ var selection = this.getSelection(); if(selection.createRange){ var range = selection.createRange(); if(range.parentElement){ var element = range.parentElement(); if(element && element.ownerDocument === this.document) this.savedSelection = range.getBookmark(); } }else if(selection.getRangeAt) this.savedSelection = selection.getRangeAt(0).cloneRange(); <<<< }, ERROR#2: Value undefined (result of expression selection.removeAllRanges() is not object. selection.removeAllRanges(); restoreSelection:function(){ this.focus(); if(!this.savedSelection) return; var selection = this.getSelection(); if(selection.createRange){ var range = this.document.body.createTextRange(); range.moveToBookmark(this.savedSelection); range.select(); }else if(selection.getRangeAt){ selection.removeAllRanges(); <<<< selection.addRange(this.savedSelection); } this.savedSelection = null; this.logSelection(); },

Suggest changing the name of this bug from "Compose Feature of Vox does not work" to "Compose new Blog Post on Vox is broken in Safari". Also suggest changing the Component to HTML DOM. Finally, suggest a higher severity given the number of VOX users who are negatively impacted who use OS X.

Trying to track this as a single "This big and complex JavaScript site doesn't work" is impractical. The issues that make it "broken" really need to be filed as separate bugs, and reduced so that they can be resolved independently.

Ok agreed. I will start opening a series of individual issues and link them here. Thanks for helping to get this some attention.

It would be ideal to use this as a master bug to track the functionality of Vox. Put the new bug numbers into the "Bug 10165 depends on:" field to track them as dependencies of this bug.

Bug 11826 (Lack of removeAllRanges() support in Webkit) has been opened. It should be linked as a dependency.

Shawn, you should be able to mark it as a dependency by putting the bug number in the "Bug 10165 depends on" field above the "Additional Comments" text area.

Re-titling as composing in Vox is no longer "broken". Adding a subtask to cover the control selections issue.

Not actionable after 15 years, closing.