Form elements in Composer/Midas are focusable

RESOLVED FIXED

Status

SeaMonkey
Composer
P1
major
RESOLVED FIXED
14 years ago
14 years ago

People

(Reporter: neil@parkwaycc.co.uk, Assigned: Aaron Leventhal)

Tracking

({regression})

Trunk
regression

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

14 years ago
Composer used to use -moz-user-focus: none !important; styles in
EditorOverride.css to prevent the user from focusing form elements e.g. input,
textarea. This no longer works, so you can now click in a textarea and start
typing into it.
See also bug 256003.
(Assignee)

Comment 2

14 years ago
Did anyone ever come up with a reliable way to tell if the current element is
part of an editable area?
Priority: -- → P1
(Assignee)

Comment 3

14 years ago
Created attachment 159810 [details] [diff] [review]
If in editor, elements are not focusable
(Assignee)

Comment 4

14 years ago
Comment on attachment 159810 [details] [diff] [review]
If in editor, elements are not focusable

Daniel, can you look to see if this is the most current foo for checkin for
whether a frame is in an editor of some kind? I'm not sure if this takes care
of the contenteditable case (is there one yet?)
Attachment #159810 - Flags: review?(daniel)
Comment on attachment 159810 [details] [diff] [review]
If in editor, elements are not focusable

r=daniel@glazman.org

We may need to do more tests the day contenteditable is in the trunk...
Attachment #159810 - Flags: review?(daniel) → review+
(Assignee)

Updated

14 years ago
Attachment #159810 - Flags: superreview?(bryner)
Attachment #159810 - Flags: superreview?(bryner) → superreview+
(Assignee)

Comment 6

14 years ago
Checking in nsFrame.cpp;
/cvsroot/mozilla/layout/html/base/src/nsFrame.cpp,v  <--  nsFrame.cpp
new revision: 3.520; previous revision: 3.519
done
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.