ok i actually cannot @ anyone on wafrn, can someone @ gabboman for me

I think it's really good if open source projects set up their own Gitlab server, to have full control over their project.
But it's super annoying to register for each,if you want to report a bug. Especially if there is no registration with Github or Gitlab sign-on.

Just found my first Firefox bug which was reproducible.

It's an awesome feeling to know that you did help even if it is a small issue found.

@app
#BugReport:
With the current public version of the app, #jaws2025 does not read the results, if any appear when a user presses alt+u to bring up the autofill menu, while composing a post.

steps to reproduce:
1. Press control+N to create a new post.
2. start typing the name of an account you'd like to mention.
3. press alt+u to bring up the autofill list.

Does #jaws2025 read it for you? If not, you've just reproduced the issue.
Now, try those same steps with #NVDA2025.
What result did you get there?
For me, it worked with #NVDA but not #jaws.
Expected behavior:
If a list of results comes up when alt+U is pressed, it should be read, regardless of #screen-reader.

Has anyone else seen this behavior?

@gabboman I really should be submitting this via the github repo but this is easier.
Trying to download pictures via a mobile browser (Opera) runs into a silly problem. When the save as menu comes up for a media attechment on a post, the file has no file type in the name as thus saves as a typeless file if i don'tinterfere. Which makes difficult to go find and rename. Its possible to rename the file before saving it to include the correct file type, but one does have to guess.
The file name is exactly 64 hexidecimal characters long, not sure if that's a hash of the file name or something, the screenshot provided truncates it to show the start and end of the name it gets.
I can grab the whole string if that helps.
Also, not sure if this is intended behavoir or not, as it could be a downscaled version of the original file as the server knows it.

I have this weird bug where I cannot write Mastodon posts nor reply on my mobile phone. I try typing in the box and nothing happens. On a reply, the keyboard shows but not the letters I type. On a new post, I can't even get the onscreen keyboard. I'm writing this from my laptop. My instance uses Mastodon v.4.3.8. My mobile browser is Firefox Android v.138.0.3. (I'm ccing my instance admin @stux just in case they know something) #Mastodon #BugReport #Firefox #Android

Fundstück von #boardgamearena

#51stState #Brettspiele #Canada #Bugreport #Trump @brettspiele