Bug happens! 
Upvoting is still the best way to show your interest, as we try to prioritize those bugs that are affecting a big portion of our users. We also fix bugs that we think are very important for everyone or bugs our MVPs brought to our attention, no matter how many upvotes it has.
Please also note that, in every release cycle, we already dedicate time to smash bugs, despite the upvote amount, or even if we don’t announce (2024r2 will come with 100+ bug fixes, as you can see in Issues)
All that said… what happens when there is a little annoyance that seems to be affecting only to you, and is going under Xojo’s radar? If you’ve upvoted 50 bugs, we have no way to know which one is your biggest priority.
With the second release of the year already around the corner, it is the perfect time to start another Bug Bash thread for 2024r3 in the Web target, like we’ve did in 2022:
Some rules
- This is a Web target event
- You can only have ONE open issue nominated, so everyone can have a bug fixed (if you paste more than one link, only the first one will participate)
- You don’t need to be the author of the bug report. Nominate a bug from somebody else, if you prefer
- While features will be considered, the priority will be fixing bugs
- If your nominated bug gets fixed, you can return here and nominate another one
The smaller the bug, the better. For example, in 2022 we had to reject the nomination of this bug, because we estimated the fix would take the whole bug bash event.
In short, if you could point one (and only one) Web bug, with a magic wand, to get it fixed in 2024r3… which one would you choose?
How to nominate your issue
Go to Issues, filter by Label=Bug and Label=Web, then paste the link of one of them in this forum thread.
Thank you for your help and for being part of this community! 
13 posts - 11 participants