Marc Durdin

Yes it's an improvement, but a keyboard that crashes every 4 minutes is not exactly stable.

> "Certain calculations" - we rely on key layout information from the DOM when noting the 'item' for each ongoing touchpath. To get this for layers currently not visible, we...

> Drilling down the other high-percentage contributors reveals similar figures - a lot of time was spent on layout-reflow. I may want to spend some time seeing if that can...

Just wondering: can we not calculate the regions without doing layout at all? We have all the numbers in the touch layout data and we have the bounding box size?

> @mcdurdin Does it make sense to use this PR (and retitle it 'Phase 1') for an A17S7 merge to master? Or would you refer _another_ PR from a chore...

> have the .kmx files in the repo because not all environments can build them, so they should be committed. Good news is that this PR is a step towards...

> Is it possible to implement hint for desktop app also We are planning to consolidate the OSK views in 18.0 or 19.0 -- to be determined -- at which...

This is now largely done. Tracking remaining issues separately.

Resolved by moving longpress menus inside the keyboard frame. See: * #9591

This is adequately fixed in v17.0, as far as I can tell. @jahorton which PR resolves this?