https://bugzilla.wikimedia.org/show_bug.cgi?id=20644
--- Comment #13 from Isarra <[email protected]> --- (In reply to comment #12) Yeah, I am something of a designer and such and I don't know the words for this either - the new messages thing is just not good. That said, I'm not sure I disagree with the close, though not reasons - the solution here ain't separate bugs on individual issues, it's chucking the entire current new messages thing and redesigning and reimplementing it properly. This could certainly be done, but given how problems for which similar solutions would make sense are rampant within LQT in general, I think a lot of the resources that might otherwise be applied to LQT are probably skirting around it in light of Flow. I know it's a ways off, but ideally Flow should resolve this stuff and serve as a replacement for LQT (and I should certainly hope the old conversations and such would be compatible, even if it does require running a script or something to transition), and poking for progress on that might help more in the long run than trying to fix up LQT now - especially when designer and developer resources are already stretched thin and trying to deal with both would only attenuate that further. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
