I've created a Javascript (ECMAScript) pop-up window with an XSLT processed form which includes a textarea element.

When one clicks on/within the textarea in the form there is no indicator that the cursor is positioned within the textarea.

All works fine and you can enter text and etc.
The mouse pointer is displayed correctly and this is not a visual mouse pointer issuse.
It's the position indicator which is normally seen an "|" within a form based textarea.

Now I haven't done the techie thing and reverse engineered the problem in K-Meleon, but the textarea does have a position indicator within the textarea of all the other major browsers which I consider to be over eight.
Even works in the three major versions of the browser of constant sorrow which shall not be named. ;-)

This may already be known or something, but I just thought I'd share.

Vulpine.

In theory K-Meleon should behave like Firefox 2 and SeaMonkey 1.
Did You check that?

p.s. & Did You check with K-Meleon Error Console?
AFAIK K-Meleon stops ECMA after first fault.



Edited 1 time(s). Last edit at 08/12/2009 11:45AM by guenter.

guenter,

I didn't check the error console. But I have now.

Error console doesn't work...???... oh. that's cause there's no errors.. ;-)

One CSS -moz error, but that's just a standards based thing.

Haven't checked FF2.0.

I was only really checking XSLT support/errors as browsers using webkit don't support xsl:import and xsl:include and I wasn't sure what sort of animal K-Meleon was, but as K-Meleon seems to support all the XSLT 1.0 features I use I wasn't to fazed about the odd little things.

woooh.. just checked another site and it uses an older version of my XSLT framework and it DOES display the cursor position in the textarea element.

So looks like it's my mistake and K-Meleon can display the cursor position in an XSLT textarea element. I probably included to much raffia work around the edges of the latest version and it's started to unravel. Just cause eight other browsers show a cursor position you just assume....

Oh well, So, all good, I can correct it if I get around to it.

Thanks all for your time.

Good to know You localized the cause.
Either SeaMonkey 1 or K-Meleon is good enough.

p.s. Thanks for Your input and info.

Unlike Firefox K-Meleon tries to exclude all non browser stuff.
I know from the past that sometimes to much was excluded.

My assumption: You used a new item not in 1.8 GRE yet?

Are these 2 related to Your work? By default K-Meleon GRE is supporting them.
# webservices, https://developer.mozilla.org/En/XML_Web_Services
# xmlextras, http://www.google.com/search?q=xmlextras



Edited 1 time(s). Last edit at 08/13/2009 06:16PM by guenter.

ooowwwhhhh....no, no.. no..

Just standard XSL 1.0 translated in Javascript (XSLT)

Using K-Meleon: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.21) Gecko/20090331 K-Meleon/1.5.3

The problem (for me) is my code is so deeply nested it's a nightmare to debug on such an obscure issue with no visible errors.

K-Meleon came into my build process at a late point as I'd already stepped through to completion with IE6, IE7 and IE8.

This works on mobile phones and browsers and takes the word unobtrusive to a whole new level.

works on fall back as follows: XSLT->AJAX->ECMAScript->XHTML/XSL/XHTML-MP/WML

One day I may construct an isolated model which can be used as a test.

One day....