menus.ContextType editable does not match a <selection> (dropdown)

[bushal (Alastair Breingan)]

Hi I am writing an extension that allows password and other data to be entered on input fields, by picking a context menu option created with contexts: [“editable”].
This works fine for input fields, but the menu option does not appear when right clicking on a field.
Thus I seem to have to use contexts: [“all”] which means the menu also appears when clicking on a non input capable element which is confusing.

I seem to recall that this once worked (some years back) - is this an oversight or am I missing something?

Thanks

[juraj.masiar]

In the docs compatibility it’s written that:

'The ‘editable’ context does not include password fields. Use the ‘password’ context for this.

menus.ContextType - Mozilla | MDN

[freaktechnik (Martin Giger)]

<select>s aren’t password fields though…

[juraj.masiar]

Yeah, I’m not a very sharp reader . Who is reading a heading? LOL!

Also his question was a bit vague, it really “felt” like he is asking for password field (and just forget the word “password”).

@bushal

when right clicking on a field.

Anyway, so select doesn’t count as editable, which makes sense I guess…

[bushal (Alastair Breingan)]

[quote="juraj.masiar, post:4, topic:84584]
Anyway, so select doesn’t count as editable, which makes sense I guess…
[/quote]

I disagree - a can have its value changed by a human viewer just as a text area can be written into, so in that regard it is editable. Certainly in my use case there is a need for either another ContextType or to regard the select as editable. My extension will populate entry fields on a page with credit card information (and others). Initially all fields are looked at and fields have their value changed to (for example) card expiry date depending on the field id and name. This works well. However some pages have weird names on fields so there is also a need to click on an individual field and state what card information should be used. Expiry dates are often shown as month and year in a dropdown .
Thus I am forced to use contexts: [“all”] which means the menu also appears when clicking on a non input capable element. This looks weird and I cannot see an other way to avoid it.

[juraj.masiar]

Maybe you can try to modify the page elements into something you can match?

Out of box idea - setting contenteditable to true on those select boxes .

BTW, how does it behave in other browsers?

[freaktechnik (Martin Giger)]

@bushal

I disagree - a can have its value changed by a human viewer just as a text area can be written into, so in that regard it is editable.

the editable context is for areas where text is editable, so where the execCommand features work etc. That is how the web generally treats “editable”.

@bushal

Thus I am forced to use contexts: [“all”] which means the menu also appears when clicking on a non input capable element. This looks weird and I cannot see an other way to avoid it.

You can hide/show the item during menus.onShown - Mozilla | MDN

[bushal (Alastair Breingan)]

[quote="freaktechnik, post:7, topic:84584]
You can hide/show the item during menus.onShown - Mozilla | MDN
[/quote]
I did not notice that possibility and will give that a go
Thank you