314987 - Find Toolbar always appears (pops up) when typing/entering "/" characters in iFrame that is in design mode, FAYT (find as you type) activated

Status: RESOLVED INCOMPLETE

(Toolkit :: Find Toolbar, defect)

Description

[Ross Dargahi (Zimbra)]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051025 Firefox/1.5

This bug has appeared in FF1.5 and is related to bug 258285. The Zimbra web client (www.zimbra.com) puts an iFrame into design mode in order to permit HTML mail message composition. In this mode typing the "/" character will always activate FAYT even if this option is deselected by the user. 

We have reproduced this on both Windows and Mac platforms

Reproducible: Always

Steps to Reproduce:
1. Create an iFrame and enable design mode 
2. Type the "/" character

Actual Results:  
FAYT gets activated

Expected Results:  
The "/" character gets entered into the iFrame

Comment 1

[Martijn Wargers (dead)]

Like at: http://www.mozilla.org/editor/midasdemo/ ?
Works for me, using the latest nightly trunk build.

Comment 2

[Ross Dargahi (Zimbra)]

After further investigation I narrowed it down to the fact that we were using 

document.open();
document.write(content);
document.close();

To populate the iFrame w/content before putting it into design mode. This would cause the iFrame to generally misbehave (one symptom being the FYAT effect, further investigation showed that execCommands were failing as well). 

switching the code to:

document.innerHTML = content;

seems to cure the problems.  

Note that this was not an issue prior to 1.5.  

Comment 3

[Martijn Wargers (dead)]

Strange, I'm not seeing that with https://bugzilla.mozilla.org/attachment.cgi?id=194116&action=view for example.
Do you see it with that example?

Comment 4

[Ross Dargahi (Zimbra)]

I just tried replacing the document.innerHTML with the document writing code in your example attachment and FF crashed. if I replace your open() call with one having no actual parameters, then things are better except FYAT starts popping up again, and no commands (e.g. trying to set bold) seem to get executed.

Let me see if I can get an example synthesised for you from our editor code 

Comment 5

[Martijn Wargers (dead)]

(In reply to comment #4)
> I just tried replacing the document.innerHTML with the document writing code in
> your example attachment and FF crashed.
Hmm, that's bad. Did you get a Talkback ID?

> Let me see if I can get an example synthesised for you from our editor code 
That would be nice.

Comment 6

[Martijn Wargers (dead)]

Ross, any luck of making a testcase?

Comment 7

[:Gavin Sharp [email: [e-mail]]]

Related to bug 304188?

Comment 8

[Martijn Wargers (dead)]

I don't think so, but I'm not sure. A testcase, or an url, would help here..

Comment 9

[Jesse Ruderman]

Dup of bug 320414?

Comment 10

[Martijn Wargers (dead)]

Ok, the zimbra demo doesn't work at all anymore in current trunk builds, because of bug 335080 and bug 335071. Bug 335071 is Zimbra's fault.
Ross, sorry to ask you again, but are you able to make a testcase for this bug?

Comment 11

[Mike de Boer [:mikedeboer]]

No testcase or solid STR available and no activity in ten years.

If you feel this issue was closed in error, please feel free to re-open.