I win!An you should encourage good bug reports by allowing developers and QA testers to give out awards. May be a special bug tracker paint job.
I win!An you should encourage good bug reports by allowing developers and QA testers to give out awards. May be a special bug tracker paint job.
It is better to supply the information twice than not at all. If you are that concerned that there is a slight chance it has been overlooked then just re-submit it. I haven't re-submitted anything on the Python Wireframe, it's been wrong for a couple of years (it was never right). If it's not fixed in the next update I'll just request a refund for the paintjob because with this change FDev will have had every opportunity to fix long standing bugs and I will be able to safely assume they have de-prioritised it.
This new process really is a step forward.
To the Circumlocution Office?![]()
Not every day I learn a new word
If in doubt, use the vernacular![]()
The ****ens, you say.
We need a way to access our old bug reports.
I think we can trust Frontier will do what Paul has said they will do, or play it safe & resubmit. It comes down to trust.
The ****ens, you say.As in Charles.
Already reported it in the Forum Problems thread.The filter is getting out of control / over zealous at this point, isn’t it![]()
What browser are you using? Maybe try a different one?I'm unable to provide a "steps to recreate" as this section will not allow me to type in it, nor paste from another texting source.
I have a bug to report regarding the last patch and unable to do so.
Have you tried another browser, as asked by Ozric?Chrome. Haven't had an issue in three past. Just recently.