Jump to content

Recommended Posts

  • 2 weeks later...
Posted

I expect as 2.0 is not broken, and 1.5 is due to be phased out when the two are merged into 2.5 that this bug isn't exactly top of their to do list.

 

Why fix something that is classed as a non-critical issue in software that is so close to the end of it's lifespan?

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...