Closed Bug 273840 Opened 20 years ago Closed 19 years ago

Cursor doesn't move through <select> element in editor

Categories

(Core :: DOM: Editor, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: sveta, Assigned: mozeditor)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616

In Internet Explorer code:
<div contentEditable="true">Tra la la. <select
onchange="changeSelOnText(this)"><option>1</option><option>2</option></select>
Tra la la.</div>
Allow edit text, choose options in listbox, fire even "onchange".
In Mozilla I can't write code, which will work like code bellow. 
I can edit text, insert or delete listbox, but I can't choose option in listbox.

Reproducible: Always
Steps to Reproduce:
1.Open http://www.mozilla.org/editor/midasdemo/
2.Set checkbox "View HTML Source" checked
3.Write in window: "Tra la la.
<select><option>1</option><option>2</option></select> Tra la la."
4.Set checkbox "View HTML Source" unchecked
5.Set cursor at the begining of the row and move cursor by rigth arrow button on
keyboard

Actual Results:  
When cursor reach <select> element, cursor jamp at the begining of the row

Expected Results:  
Cursor must set focus on <select> element and then move on
Mats, didn't you run into this recently?
The closest one I can think of is bug 268497 but that's a different problem,
I think.

I do see the described behaviour in Mozilla 1.7.3 on Linux, but the
"Actual Results" is different in a 2005-01-11 trunk Linux build.
The caret does not jump to the beginning, it ends up on the right side of the
<select>. (The caret does not seem to enter into the <select> though).
If I change the select to <select multiple="multiple"> then I can at least
edit one of the options (2), but I can't navigate to the other.
This bug seems more like a keyboard navigation problem.
OS: Windows 2000 → All
Ginn Chen is the man who knows about these kinds of bugs.
Do we need choose option in midas?
I don't think so.

But I can't go through the following HTML by right arrow(left arrow works), it
may be a bug.
Tra la la. <select multiple="multiple"><option>1</option><option>
2</option></select> Tra la la.
Dear Ginn Chen, in IE  in <div contentEditable="true"> it is possible to use
<select> tag and choose options. This allows to create aplications where there
are the templates which can be edited by users. Therefore, to choose <option> in
midas is very important for us. Furthermore, to catch event onchange from tag
<select> is also useful.
Is it a feature request of midas?
It's not only a keyboard navigation bug, I can't choose a option in midas by
mouse, either.
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/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.