Describe the bug
When creating a 'shortcut' (PWA) with the Brave Browser (based on Chromium) on macOS 10.15.1 it immediately throws the following error:
2019-12-04 17:30:20.202 app_mode_loader[32295:1717699] -[NSAccessibilityRemoteUIElement accessibilityTitle]: unrecognized selector sent to instance 0x7fe76de4e7d0
2019-12-04 17:30:20.204 app_mode_loader[32295:1717699] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSAccessibilityRemoteUIElement accessibilityTitle]: unrecognized selector sent to instance 0x7fe76de4e7d0'
I've detailed this bug on Github with brave-browser here: https://github.com/brave/brave-browser/issues/7205. After some digging though it seems that disabling BetterSnapTool (in full or just for the Brave Browser specific app I've created) makes the problem go away (although I lose the BST functionality). I've seen some Chrome-related bugs on this forum before, but it's interesting that with the regular Chromium and BST this bug doesn't happen.
- Type of Mac: Macbook Pro 13" 2018
- macOS version: 10.15.1
- BetterSnapTool 1.9.2.
Additional information (e.g. StackTraces, related issues, screenshots, workarounds, etc.):
See the related information on the Github bug report: https://github.com/brave/brave-browser/issues/7205
@Andreas_Hegenberg any clues what might be causing the bug above?
unfortunately that’s a bug in Brave Browser where it doesn’t seem to implement a specific functionality of the standard macOS accessibility API (or is forwarding the request to some wrong object) . This can’t be fixed in BetterSnapTool
The specific selector that should be available, but unfortunately isn’t is „accessibilityTitle“
Thanks for the pointers. I'll try and see what's happening with Brave - the weird thing is that it is implemented in the Chromium browser which Brave is based on, but apparently not in the Brave-implementation: https://github.com/chromium/chromium/search?q=accessibilityTitle&unscoped_q=accessibilityTitle
Maybe Brave uses a different kind of custom window for more customisability or something like that. In that case they should either disable Accessibility support completely for that window or implement all the required methods (or at least add stubs so it won't crash when macOS calls them).
BetterSnapTool is definitely not the only tool that will cause a crash here
Thanks @Andreas_Hegenberg! I've expanded the bug report with Brave and hopefully they'll be able to fix it.
I'm a software engineer at Brave. This issue has been affecting me for a while too, to the point where I have to run without BTT a lot of the time, sadly. I'd like to look in to fixing this on Brave, but as far as I know, we do little customization in this area compared to Chromium. I'll dig in though.
I actually only get the crash when moving the window (either dragging with mouse normally, or with the BTT keyboard modifier shortcut for window moving)
Any updates on this? I really wish I could use brave PWAs (especially for asana and youtube) instead of having to use the chrome PWAs or directly access them in the Brave Browser. I really wish the apps wouldn't crash when I try to move them while BTT is running…
Update: seems to be resolved now! Tested on 2018 13" MacBook Pro (Big Sur) and M1 MacBook Pro (Big Sur)