You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That said, one notable issue with setKeyboardForControl with iframe elements - especially non-design-mode ones - is that they may contain multiple elements. It is technically possible, I believe, to call setKeyboardForControl on each of those elements.
This then raises the question: what should setKeyboardForControl actually do in this scenario? Should it iterate over all of the iframe's internal elements and use setKeyboardForControl on each? This seems the simplest solution.
setKeyboardForControl should only be used on iframes which are in designmode=true. It's intended for use for a single edit element, whether that is an input, textarea, div+contentEditable, or iframe+designMode.
We probably should even test for that and throw if caller attempts to setKeyboardForControl for any non-design-mode iframe.
Reference: https://stackoverflow.com/questions/69694488/keyman-setdefaultkeyboardforcontrolpelem-keyboard-languagecode-function-is
A user asked asked how to get
setDefaultKeyboardForControl
to work with an iframe element.It's currently a system limitation that @mcdurdin says
The text was updated successfully, but these errors were encountered: