If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Editor can't override default form field behaviour




Layout: Form Controls
15 years ago
8 years ago


(Reporter: neil@parkwaycc.co.uk, Assigned: John Keiser (jkeiser))



Firefox Tracking Flags

(Not tracked)




15 years ago
I was looking into getting editing working for form fields but I'm running into
some problems. I have found that using a style rule of -moz-user-input: enabled
(instead of none which interstingly does have the effect of disabling events to
the field) in EditorOverride.css will allow double-clicking and context menus to
work on fields for the most part, but there is still some unwanted behaviour
that there does not appear to be any way to block:
1. If you set the disabled attribute then you can't select or click the field.
   I feel that -moz-user-input: enabled !important; should override this.
   forms.css should probably use [disabled] { -moz-user-input: disabled; }
2. A checkbox or radio button visually checks itself when you click it.
   I feel that -moz-user-modify: read-only !important; should override this.
   forms.css should probably use [readonly] { -moz-user-modify: read-only; }
   to override the default which should be read-write (write for password?).
3. The options in a list box become clickable.
4. The drop-down list can still be dropped down using the dropmarker.
   I feel that there should be styles I can set to prevent these.
5. Single-clicks don't select fields (although double and context clicks do).
   I feel there should be a -moz-user-select: style to enable this.

Comment 1

15 years ago
This is essentially a bug to specify form control behavior in CSS.  I agree with
this.  Examples of what you're trying to do would be helpful though.
Priority: -- → P3
Target Milestone: --- → Future

Comment 2

15 years ago
What would be nice is if Editor could use CSS to ensure that (double-)clicking,
and context menu on form controls should simply select the control (even when
the control has the disabled attribute) bypassing normal control behaviour.
Currently disabled controls are virtually unusable in Editor while other
controls are at best partially usable using -moz-user-input: enabled !important;
in CSS.
QA Contact: tpreston → layout.form-controls
You need to log in before you can comment on or make changes to this bug.