Last modified: 2013-09-14 23:39:31 UTC
I can see how some people might like the "clean" organization this extension provides, but personally it gets in the way of my workflow. It needs to be optional, just as the "enhanced recent changes" are.
I believe this extension is tied into the "enhanced recent changes" user preference in order to reduce user preferences clutter. What don't some people like about "cleanliness"?
No, it's not. I have that preference disabled and I still see a screwed-up watchlist. As for "cleanliness", like beauty it is in the eye of the beholder.
Actually, scratch that. Somehow the preference got enabled despite my never actually enabling it. Turning it off restores a normal watchlist appearance.
(In reply to comment #3) > Actually, scratch that. Somehow the preference got enabled despite my never > actually enabling it. Turning it off restores a normal watchlist appearance. Yes, this seems to be the most controversial aspect of the deployment. CleanChanges was made opt-out rather than opt-in. :-)
Niklas: can you comment on the design decision here?
It's not clear what you want me to comment. It replaces the enhanced changes list because I think it is an improvement and more choice is not better. The extension doesn't change anyone's preferences.
(In reply to comment #3) > Actually, scratch that. Somehow the preference got enabled despite my never > actually enabling it. Turning it off restores a normal watchlist appearance. Should the bug be closed WORKSFORME?
While I agree that it should be disabled by default, that's an issue. I have to say that there is in fact an off switch, although it's switched on by default.
