[Mozile] Mozile 0.6.22.7 for Firefox 1.5 and up now available. BUG

Jon Schull jschull at softlock.com
Sat Feb 4 17:14:54 EST 2006


On Feb 4, 2006, at 5:06 PM, Max d'Ayala wrote:

> Hi Jon.
>
> Unfortunately this is a known issue and is probably mentioned in  
> the docs somewhere.

sorry I missed that

>
> At the moment, the 0.6 Series will only work if the top editable  
> element is a "div", or "body".

Maybe I'm not understanding:  I just added a div as the top editable  
element, and it still breaks:

<html>
   <head></head>
<body>

<style>
   div{
   -moz-user-modify: read-write;
   -moz-user-input: enabled;
   -moz-user-select:text;
   background:pink;
   }

    #prior{
   -moz-user-modify: read-write;
   -moz-user-input: enabled;
   -moz-user-select:text;
   background:pink;
   }

</style>
<div>hello</div>
<hr>
<span id="prior">
   this is editable but I get an error when I hit carriage return
</span>
<pre>
[JavaScript Application]
   Selection.splitXHTMLLine: TypeError: nodeToTest has no properties
</pre>
</body>
</html>
>



>
> I'm not sure if Mozile has ever worked correctly for other elements.
>
> There are two reasons for this. First, the appropriate logic has  
> never been built into the eDOMXHTML.js code. So if you make a span  
> editable you should be able to edit the text, but if you press  
> return it will cause an error because it will treat the "span" as  
> though it were a "div". i.e. It will (try to) split the text into  
> two paragraphs.

that actually makes sense.  Although inserting <br> breaks would be  
the "obvious" solution


>
> I have no intention of writing the code for this in the near  
> future, if at all.
>
> The other way round this would be to use a different MES for  
> editing spans and use the key override feature. Unfortunately,  
> nobody has ever finished this part of the code - so it can't be  
> done this way either. The main disadvantage with this method is  
> that you wouldn't be able to edit a mixture of block level elements  
> and inline elements, such as div's and span's, on the same page  
> because you can only have one MES per page. There is a possibility  
> that I may complete this part to get round the problems with the  
> break element.
>
> (Key overrides would work by specifying which command you want to  
> be executed with a  key such as Enter and Tab. So for the Enter key  
> you could either specify a command that did nothing, or possibly  
> enter a break element instead.)
>
> Max
>
>
> PS Do you have to set a preference or option to get the spacebar to  
> page down?
>
> _______________________________________________
> Mozile mailing list
> Mozile at mozdev.org
> http://mozdev.org/mailman/listinfo/mozile
>



More information about the Mozile mailing list