Thanks for the clear feedback! > > This part is obvious. The problem we need to solve is that at the > Address or the Subscription level, the user wants to know both the > *effective* value and where that value was set. > Maybe This can be handled to some extent by sorting the rows, but I'm > not sure that's a great user experience. Does Postorius already have a preferred UI pattern (like badges or muted text) to show inherited versus overridden values, or should I propose a new visual indicator for this in my UI mockups? > > This is correct behavior. > > I think the solution to this is to label it "User default" rather than > "Global". This task is about addressing confusion by improving > visibility of the settings. Adding documentation that User-level > settings may be overridden by Address or Subscription settings would > be acceptable, but I think changing process (especially adding > confirmation steps) should be left until users ask for it or express > confusion about it. That makes complete sense. I will drop the confirmation check idea and focus strictly on improving the visibility and in-app documentation of these settings.
> > Behind the presentation. which appears to be a matrix of SELECT > elements, in fact the rows should be heterogeneous: rows that handle > setting for User (user-only), List (admin-only), Address (user-only), > and Subscription (both) settings, and display List (user-only). Since > the views are different, the selection logic is trivial. I'll make sure to outline this rendering logic clearly in my proposal. I am currently working on a rough UI sketch to address the "effective value" problem and will share a link to my draft proposal doc soon. Thanks again for your time! _______________________________________________ Mailman-Developers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
