Closed nikku closed 9 hours ago
@nikku , assigned to you for now to clarify what is needed to enable HTO team
@vsgoulart I'll not be able to follow up on this in the next days, but will revisit end of March.
Assigning to @jarekdanielak to assess in a timebox manner.
Explanatory scetch, based of discussion with @jarekdanielak:
Existing ways to indicate breaking changes (APIs no longer working or changed) - https://github.com/search?q=repo%3Abpmn-io%2Fdiagram-js%20console.warn&type=code.
Other editors, e.g. code mirror are great examples for friendly, and accessible integration into the browser.
Is your feature request related to a problem? Please describe.
For historical reasons our users had to bind
keyboard
to any element on the page, may it be document, or the diagram container. With https://github.com/bpmn-io/diagram-js/pull/662 we make the diagram canvas browser selectable; as such we can safely figure out if the canvas has focus and keyboard bindings shall be accounted for.Because of that we want to remove the bind anywhere
keyboard#bindTo
/keyboard#bind(element)
APIs.Describe the solution you'd like
keyboard.bindTo
is removedcanvas.focus()
, and potentiallydiagram.focus()
as a proxy) existfocus
andblur
events that I can hook into to register global keyboard shortcutsDescribe alternatives you've considered
Keep stuff and magic as is.
Additional context
This is a major improvement UX wise.