FYI -- did some basic telemetry testing, looks like `isFullKeyboardAccessEnabled` is controlled by both this new preference AND the old/existing keyboard preference. so that's cool.
Bug 1772375 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
FYI -- did some basic telemetry testing, looks like `isFullKeyboardAccessEnabled` is controlled by both this new preference AND the old/existing keyboard preference. so that's cool. EDIT: ah, the new feature _also_ enables the old one, but you can manually disable the old one and have just the new one on. The new one does set AXEnhancedInterface, though where the old one doesn't. So something like this describes the behaviour: both enabled -> `AXEnhancedUserInterface && isFullKeyboardAccessEnabled` new feature, but not old -> `AXEnhancedUserInterface && !isFullKeyboardAccessEnabled` old feature, but not new -> `!AXEnhancedUserInterface && isFullKeyboardAccessEnabled `
FYI -- did some basic telemetry testing, looks like `isFullKeyboardAccessEnabled` is controlled by both this new preference AND the old/existing keyboard preference. so that's cool. EDIT: ah, the new feature _also_ enables the old one, but you can manually disable the old one and have just the new one on. The new one does set `AXEnhancedUserInterface`, though where the old one doesn't. So something like this describes the behaviour: both enabled -> `AXEnhancedUserInterface && isFullKeyboardAccessEnabled` new feature, but not old -> `AXEnhancedUserInterface && !isFullKeyboardAccessEnabled` old feature, but not new -> `!AXEnhancedUserInterface && isFullKeyboardAccessEnabled ` `AXEnhancedUserInterface` will also be set when VO is enabled, though (among other things), so this isn’t specific enough to know the new feature is on