Conversation

Notices

1. Embed this notice
   Simon Jaeger (simon@dragonscave.space)'s status on Wednesday, 03-Apr-2024 02:17:39 JST Simon Jaeger

   • Andre Louis
   • bryansmart
   • NV Access

   @FreakyFwoof @bryansmart If someone at @NVAccess wants to do this before I get done with work, feel free. otherwise, I will.

   • Embed this notice
     Talon (talon@dragonscave.space)'s status on Wednesday, 03-Apr-2024 02:17:32 JST Talon

     in reply to

     • Andre Louis
     • Tyler Spivey

     @simon @tspivey @FreakyFwoof From the issue: I can see no point in setting up people with CAPS LOCK by default when that changes the behavior of the CAPS LOCK key when using it for its native purpose. That's just asking for unnecessary confusion, whether Narrator does it or not.
     lol but the insert key is fine? That one also has a native purpose, you know. Also capslock is one of my least used keys for its intended purpose. In fact, every single time, and I do mean literally every single one as far back as my memory goes, turning capslock on was a mistake, and not something I actually wanted. Am I alone here? I always use laptop layout. Always. Even on desktop keyboards. I don't even have to think about it at all, it should be on by default.
     You have two options. Option one only works on some keyboards, option 2 works on all keyboards. Which one do you pick? I know which one I'm picking.

   • Embed this notice
     Simon Jaeger (simon@dragonscave.space)'s status on Wednesday, 03-Apr-2024 02:17:34 JST Simon Jaeger

     in reply to

     • Andre Louis
     • bryansmart
     • NV Access
     • Tyler Spivey

     @tspivey @FreakyFwoof @bryansmart @NVAccess Why amI not surprised this is ancient?

     GreenSkyOverMe (Monika) repeated this.
   • Embed this notice
     Tyler Spivey (tspivey@dragonscave.space)'s status on Wednesday, 03-Apr-2024 02:17:38 JST Tyler Spivey

     in reply to

     • Andre Louis
     • bryansmart
     • NV Access

     @simon @FreakyFwoof @bryansmart @NVAccess This? https://github.com/nvaccess/nvda/issues/11678