[Mozile] Mozile 0.6.23 Released

Max d'Ayala max at dayala.co.uk
Fri Feb 10 17:41:36 EST 2006


Hi All.

Download 0.6.23 for Firefox 1.5+ only:

http://downloads.mozdev.org/mozile/

Or here if the mirrors haven't updated yet:

http://www.dayala.co.uk/mozile/test/Docs/mozile-0.6.23-devel.xpi


The new version contains a few additions as listed below.

Changes to Mozile between 0.6.22.7 and 0.6.23

Mozile 0.6.23 - 9 Feb 2007

Options
The enable/disable Mozile option has been reworded to avoid any 
confusion with the extension
enable/disable option. The alert saying that Mozile is switched OFF has 
been removed. The toolbar
icons are now dimmed when Mozile is switched off. Clicking the toolbar 
buttons doesn't do anything.
Shortcut added - double click Mozile menu to toggle ON/OFF.

Caret and Navigation
Some changes made to insertion point forward movement to fix bugs to do 
with getting stuck when an
image is at the end of a line. Some changes made to insertion of <br/> 
element. Seems to be working
better, although code to correctly handle deletion of break and 
whitespace in one go, and the handling
of an editing token when <br/> is at the end of the line remain.

XHTML Line Splitting (Enter key)
I've added a lookup table to check if splitting can occur. This stops 
splitting if you make Line
containers such as "p" or "h1" the top editable element, or if you use 
inline elements such as "span" as
the top editable element. Not all commands check if what they do is 
valid. E.g. you can incorrectly
change the line container when "span" is the editable element. Hence, 
currently difficult to mix editing
of div's and span's with the same MES.

Demos
Added an additional demo so that you can test what happens with "div", 
"p" or "b" as the top editable
element.

CVS
All the files should be in CVS now in the following folder:
mozile\source\extension\mozile-0.6

MES
The commands to change the font were incorrect in mes-XHTML.xml and 
didn't work.
(The same commands were correct in mes-XHTML-test.xml)


Bugs
I noticed a bug I hadn't seen before. The styleLines command, used to 
set the line justification,
doesn't work correctly if you just have a single line in the editable 
div. I'll correct this in the
next release.

Keep the bug reports coming in, no matter how small the bug. I've made 
the first step towards
editing "p", "span", etc by correcting the XHTML split line command. It 
will be interesting
to find out how many other commands need to be fixed to allow error free 
editing in these
cases. Also, let me know if the split line command has stopped working 
when it shouldn't.

Thanks,

Max








More information about the Mozile mailing list