Closed Bug 258937 Opened 21 years ago Closed 21 years ago

Form elements in Composer/Midas are focusable

Categories

(SeaMonkey :: Composer, defect, P1)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: neil, Assigned: aaronlev)

Details

(Keywords: regression)

Attachments

(1 file)

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.
Did anyone ever come up with a reliable way to tell if the current element is part of an editable area?
Priority: -- → P1
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+
Attachment #159810 - Flags: superreview?(bryner)
Attachment #159810 - Flags: superreview?(bryner) → superreview+
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
Closed: 21 years ago
Resolution: --- → FIXED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: