← Back to context Comment by criley2 3 days ago They're not fixing it, they're "changing" it, which makes sense, because the design changed. 5 comments criley2 Reply chrisjj 3 days ago > They're not fixing it"It's already been fixed as part of v2.1.281 releasing today." criley2 3 days ago Developer comms are very important. I've often "fixed" something that was working exactly as the designer made it. It certainly wasn't a bug in my work though. I've worked in places where we call this a "design omission" ;) chrisjj 3 days ago No omission seen in this case, though. 1 reply → mort96 3 days ago Design bugs are still bugs
chrisjj 3 days ago > They're not fixing it"It's already been fixed as part of v2.1.281 releasing today." criley2 3 days ago Developer comms are very important. I've often "fixed" something that was working exactly as the designer made it. It certainly wasn't a bug in my work though. I've worked in places where we call this a "design omission" ;) chrisjj 3 days ago No omission seen in this case, though. 1 reply → mort96 3 days ago Design bugs are still bugs
criley2 3 days ago Developer comms are very important. I've often "fixed" something that was working exactly as the designer made it. It certainly wasn't a bug in my work though. I've worked in places where we call this a "design omission" ;) chrisjj 3 days ago No omission seen in this case, though. 1 reply → mort96 3 days ago Design bugs are still bugs
> They're not fixing it
"It's already been fixed as part of v2.1.281 releasing today."
Developer comms are very important. I've often "fixed" something that was working exactly as the designer made it. It certainly wasn't a bug in my work though. I've worked in places where we call this a "design omission" ;)
No omission seen in this case, though.
1 reply →
Design bugs are still bugs