Closed
Bug 315454
Opened 19 years ago
Closed 4 months ago
Find as you Type is not disabled when an editable <iframe> is added to a document using the DOM
Categories
(Core :: DOM: Editor, defect, P5)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: tommy, Unassigned)
References
()
Details
Attachments
(2 files)
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 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 When you add an <iframe> using DOM methods, find as you type is not disabled. If the <iframe> is manually written into the page and you simply use script to enable designMode, find as you type is correctly disabled. Reproducible: Always Steps to Reproduce: 1. Create a simple html document. 2. Add a script that will create an <iframe> using document.createElement 3. Insert the new node using someNode.appendChild(newNode) 4. Enable designMode on the new <iframe> Actual Results: A somewhat functional editor is created, but find as you type is still enabled. Expected Results: Find as you type should be disabled.
Reporter | ||
Comment 1•19 years ago
|
||
Reporter | ||
Comment 2•19 years ago
|
||
Comment 3•19 years ago
|
||
With the first testcase, designMode isn't working at all. You probably need to write this code in a separate function: function doe(){ editor.contentWindow.document.designMode = "on"; } and then call doe in a timer inside init(): setTimeout(doe,500); Then it should work. The problem is that the iframe is not really 'ready' to set designMode on.
Reporter | ||
Comment 4•19 years ago
|
||
(In reply to comment #3) > With the first testcase, designMode isn't working at all. I've noticed that sometimes when I load that testcase designMode isn't enabled. I don't know why that is. I threw the testcase together very quickly. If you reload the page designMode will be enabled and you can see the faulty behavior I'm talking about. I'll see if I can create a better testcase.
Updated•17 years ago
|
QA Contact: editor
Updated•17 years ago
|
Assignee: mozeditor → nobody
Comment 5•3 years ago
|
||
Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority.
If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.
Severity: normal → S4
Priority: -- → P5
Comment 6•4 months ago
|
||
See the testcase: https://jsfiddle.net/d_toybox/gq5v8wf7/show
designMode document does not steal focus. Therefore, FAYT should keep being ready until the sub-document gets focus.
-> WFM
Status: UNCONFIRMED → RESOLVED
Closed: 4 months ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•