Alex,
The browsers that I am testing with include ff, ie, chromium and opera. It
appears to me that the 'forceEditable' method that you mention does not do
anything except for a gecko based browser ( ff ).
I will see if I can't put together simple sample code to show the problem.
But in the meantime, is there not a way to force the HtmlArea to be editable
if it is not gecko? I have tried setting the content editable and setting
the designmode, but to no avail. Following is the code in HtmlAreaNative.js
for 'forceEditable' which specifically checks for Gecko, and all other
browsers fall through to the default.
tom
/**
* Forces the htmlArea to reset the document editable. This method can
* be useful (especially for Gecko) whenever the HtmlArea was hidden and
* gets visible again.
*/
forceEditable : qx.core.Variant.select("qx.client",
{
"gecko" : function()
{
var doc = this._getIframeDocument();
if (doc)
{
/*
* Don't ask my why, but this is the only way I found to get
* gecko back to a state of an editable document after the
htmlArea
* was hidden and visible again.
* Yes, and there are differences in Firefox 3.x and Firefox 2.x
*/
if (qx.bom.client.Engine.VERSION >= "1.9")
{
doc.designMode = "Off";
doc.body.contentEditable = false;
doc.body.contentEditable = true;
}
else
{
doc.body.contentEditable = true;
this.__setDesignMode(true);
}
}
},
"default" : function() { }
}),
Alexander Steitz wrote:
>
> Hi Tom,
>
> On Thursday 08 October 2009 tsmiller wrote:
>> The problem: (all major browsers except IE have this problem. Safari has
>> not been tested)
> I'm aware of problems for gecko, but there is a mechanism that
> automatically
> forces the HtmlArea into editable mode at each "appear". With "all major
> browsers" you mean Gecko and Opera?
>
>> I create a window that contains a window that contains a qooxdoo HtmlArea
>> that is added to my main desktop.
>>
>> After adding (moving) this window to a different container (to save for
>> later use) and then back to the desktop, the HtmlArea will not become
>> editable again. Can anyone tell me why this happens and is there a sure
>> fire method to force the HtmlArea editable again in all of the browsers.
> The method's name is "forceEditable" and this method is called whenever
> the
> "appear" event is fired. So this should be executed when you display the
> window
> again.
>
> If this does not solve your problem feel free to file a bug report for
> this.
> Inlcuding some code would be very nice to easily reproduce this issue.
>
> ->
> http://bugzilla.qooxdoo.org/enter_bug.cgi?product=contrib&component=HtmlArea
>
> cheers,
> Alex
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
--
View this message in context:
http://www.nabble.com/Cannot-make-HtmlArea-editable-8.3-tp25803295p25822840.html
Sent from the qooxdoo-devel mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
