Open Bug 236113 Opened 20 years ago Updated 3 years ago
Midas - it is difficult to get the focus to go to the element with design
(Core :: DOM: Editor, defect, P5)
(Reporter: osavill, Unassigned)
User-Agent: Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7a) Gecko/20040218 Using the straight demo at http://www.mozilla.org/editor/midasdemo/ create a table. Now, straight away create another one. This will result in a Java Script exception because the editable IFRAME did not have the focus when the second table was created. Adding document.getElementById('edit').contentWindow.focus(); makes no difference. However, removing focus completely from either the browser tab or the entire browser and then going back to the editor page results in the cursor flashing where it should. The first time the page is visited, and each time it is refreshed, it is possible to start typing in to the editable field even though no cursor is showing, so it at this point it does have the input focus but not after table insertion. Reproducible: Always Steps to Reproduce: 1. 2. 3.
20 years ago
Assignee: general → mozeditor
Component: Browser-General → Editor: Core
QA Contact: general → bugzilla
Summary: Editor: Midas - it is difficult to get the focus to go to the element with designMode="on" → Midas - it is difficult to get the focus to go to the element with designMode="on"
18 years ago
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
16 years ago
QA Contact: bugzilla → editor
16 years ago
Assignee: mozeditor → nobody
13 years ago
This problem still exists for me on firefox 3.6.3. After setting the selection manually on a designmode-on-iframe, I can't get the selection to visibly appear unless i switch I browser tabs, or call alert(), although the focus is actually there. It looks like the selection simply isn't being drawn. calling focus() on a textarea, and then on the iframe again, seems to be a workaround
13 years ago
[firefox 3.6.3] The focus() and blur methods seem to be a little messed up. When u have :focus (writing something) on an editable=true element you cant remove it by calling .blur() on the element. But indeed the shadow around the element indicating that you are editing disappears. So it happens that you call blur on :focus element but the elemnt keeps catching keystrokes. (Annoying when you try to make something keynavable)
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
You need to log in before you can comment on or make changes to this bug.