Keyboard-event handling is based on the deprecated charCode property of DOM Events

[daboe01]

this needs to be addressed in the future as we are currently working around unexpected behaviors, i.e. for more recent FireFox versions.

[cappbot]

Milestone: Someday. Label: #new. What's next? A reviewer should examine this issue.

[enquora]

@daboe01 Can you change 'depreciated' to 'deprecated' in your issue title? It is the correct terminology and in this case may cause problems when searching issues.

[enquora]

Keyboard navigation of CPOutlineView is non-functional in Firefox (haven't checked CPTableView yet). Perhaps this is the reason? Still functional in much earlier versions of Firefox and WebKit/Blink browsers.

[enquora]

https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent indicates (suggesting the root of the problem wrt modern Firefox):

As of Firefox 65, the keypress event is no longer fired for non-printable keys (bug 968056), except for the Enter key, and the Shift + Enter and Ctrl + Enter key combinations (these were kept for cross-browser compatibility purposes).

The compatibility chart also indicates weak support for the modern API wrt Internet Explorer 9. Are we still concerned with support for any version of IE (Microsoft isn't)?

[daboe01]

@enquora your FF issues should be fixed in latest master. see #2874

[enquora]

@daboe01 The Firefox problem occurs using current master, but I'll re-check and refer comments to #2874 if appropriate.

[daboe01]

@enquora i just checked with FF76 on mac. here, keyboard navigation works with collectionview and tableview (not tested outlineview, though).

[enquora]

@daboe01 Confirmed that the minimal CPOutlineView manual test (from Cappuccino source) works as expected in all browsers. These problems are in several of our apps. There are no obvious handlers in the responder chains which might account for this - it will be necessary to reduce the app to isolate the behaviour and determine if it is caused by application code or a non-obvious interaction within Cappuccino itself.

[daboe01]

@enquora just guessing, could it be that the firstresponder state of you outlineview is lost somehow?

[daboe01]

-#new
+AppKit

[daboe01]

+#acknowledged

[cappbot]

Milestone: Someday. Labels: #acknowledged, AppKit. What's next? A reviewer should examine this issue.