@joefutrelle , at first I was going to build out this functionality, but then I noticed we're already keeping track of the last 5 recent labels. It was a very quick change to set the \<select> to whatever recent_labels[0] is. The trouble is, because it's using local storage, it's persisting on refresh, and would take extra inelegant logic to make it match the filter_label select on refresh.
So, The only way a user would see the "[The new behavior where the default assign label matches the view label at first is good--it should only do that when we first load the class page though.]" is if they have never applied a label, and their recent_labels store is empty.
It feels like this would be simpler and slicker - let me know what you think and I can make it work either way.
@joefutrelle , at first I was going to build out this functionality, but then I noticed we're already keeping track of the last 5 recent labels. It was a very quick change to set the \<select> to whatever
recent_labels[0]is. The trouble is, because it's using local storage, it's persisting on refresh, and would take extra inelegant logic to make it match the filter_label select on refresh.So, The only way a user would see the "[The new behavior where the default assign label matches the view label at first is good--it should only do that when we first load the class page though.]" is if they have never applied a label, and their
recent_labelsstore is empty.It feels like this would be simpler and slicker - let me know what you think and I can make it work either way.