Open Bug 1611308 Opened 2 years ago Updated 2 years ago

Some context menu items that modify values should be disabled for disabled form controls

Categories

(Firefox :: Menus, defect, P3)

defect

Tracking

()

People

(Reporter: MattN, Unassigned)

References

Details

(Keywords: parity-chrome, parity-safari, Whiteboard: [passwords:fill-ui] [passwords:generation])

The following menu items (which isn't an exhaustive list) should IMO be disabled on disabled form fields e.g. <input>:

  • Cut
  • Paste
  • Fill Login/Password
  • Use generated password…
  • Spelling suggestions

Perhaps onEditable should be false for @disabled fields like it is for @readOnly… but then that makes me think perhaps SpellCheckHelper.EDITABLE should also be false in this case…

Perhaps the spell checker underline should also be removed in this case?

This was last changed in bug 1345081, and also has some extension implications (though we could diverge the two if we really wanted, it seems like we should ideally share a concept of what's editable). :zombie, do you know what other browsers do wrt the webext api?

Flags: needinfo?(tomica)
See Also: → 1345081

P3 from a menus perspective, I think, though if this is on pwmgr radar that might get its own priority?

Priority: -- → P3
See Also: → 1612122

Yeah, this seems like a good idea, a disabled input is even less "editable" than a read only one, and we already don't include "editable" flag for those. And from the cursory look, Chrome seems to agree.

Flags: needinfo?(tomica)
You need to log in before you can comment on or make changes to this bug.