I'm having an issue with #Firefox and Semaphore. After it's been running for a while, the Semaphore tab gets to very high CPU usage, with about:performance indicating around 160%. This seems to be a regression with firefox 134, as it didn't use to happen before.
Any clues what I can do about this, or whether I should report a bug?
@modulux I'm a bit worried because Pinafore and Semaphore are unmaintained. You cannot even open an issue to Semaphore. I'm using Enafore, which is mildly active.
You could try what happens with Enafore.
Otherwise, I think all three are based around an outdated version of Svelte... you could open a Firefox bug? But I wouldn't put a lot of hopes there :(
@yo Enafore doesn't do focus control properly so that's a no. But yes, it is a pity that they're abandoned.
@modulux I use Enafore because of its keyboard support, but I'm already having some issues with it (it doesn't support multiple accounts in the same server).
I am not aware of good accessibility-friendly Mastodon clients :(
@yo that's the thing, the keyboard support is regressed from Pinafore/Semaphore. For example activating the more options button, you can't use up and down arrow to move down the menu without some focus screwyness first. Other problems like that: in the compose dialogue if you activate the visibility button to change visibility, up and down arrow won't get you through the options.
@modulux ouch, the person pushing to Enafore does not even have a public GitHub account. I wouldn't mind sponsoring with a bit of money there. If you ever find someone willing to invest time in an accessible, keyboard-friendly Mastodon client, I wouldn't mind donating some money.
(If there's in general any place worth supporting to push for accessible software, I'd be all ears.)
