Comment 46 for bug 1888723

Thanks for the feedback, everyone. Looking at these now.

Regarding the Apply, how does everyone feel about the XUL-style display where it shows the value counts by default instead of the form input for changing the value? In other words, the way you have to "activate" the field to change its value?

Another purpose of the Apply button is to indicate when the edit action for a field is complete, allowing the display to return to the value counts/summary view. (It could be based on watching the onchange of the input, but I worry that would lead to a lot of unintended field edit deactivations). If we lose the Apply, we have to reconsider how/where the summary counts are displayed.

I'll note one of the decisions leading to the current implementation was our staff wanted the summary counts to be visible on page load instead of hidden in drop downs. We could go back to that, but I suspect others may like the return of the up-front summaries -- correct me if I'm wrong!

We could display the summaries AND the form inputs. Would that be too busy?