Bad UX - backend - if views are empty #32956
Replies: 7 comments
-
Why should there be nothing? |
Beta Was this translation helpful? Give feedback.
-
according to me this info-alert box should come only when a user search something and don't get the required result , it will prevent confusion. |
Beta Was this translation helpful? Give feedback.
-
This is right. We could differ between "There is no override yet" and "no matching result". |
Beta Was this translation helpful? Give feedback.
-
Yes, but then it should be done consistently everywhere, not only for the overrides, i.e. "There is no %s yet" or something like that in all list views where no item exists yet, and "No matching result" if a search or filtering gives no result. I can imagine that people think that the word "matching" in the message refers to a search or filtering, so I can understand the motivation behind this issue (which I would say is an RFC). Personally I can live with it like it is, but that's maybe because of my developer point of view. |
Beta Was this translation helpful? Give feedback.
-
It would not be a simple change to make across all the uses. This is because a lot of the views are actually filtered even if you dont realise |
Beta Was this translation helpful? Give feedback.
-
Exactly that's why at the end I can live with like it is now. |
Beta Was this translation helpful? Give feedback.
-
It is worth a discussion, but surely not in 4.0. |
Beta Was this translation helpful? Give feedback.
-
Problem identified
on going on system>language>language-overrides ,there is a text bar with 'no matching result' written on it without even searching something, the same issue happens on other pages also example component>banner, tracks .
It occurs when there is no data on the page.
Proposed solution
Instead of info-alert nothing should be there.
Beta Was this translation helpful? Give feedback.
All reactions