-
Notifications
You must be signed in to change notification settings - Fork 19
[QA] show 'pending' when the folder size is not yet computed #1402
Comments
We did not implement 'pending' based on @hodyroff 's request - please make a final decision. Please also take into consideration the UX report as delivered by Andreas today - see rocketchat channel for phoenix |
if we do not port this feature 1-1 from OC 10 we need to document the discrepancy in the product docs @pmaier1 |
@tbsbdr please check this out. My personal opinion is what I did in the project, "pending", ? or 0 bytes is confusing. If we can't guarantee we can show the proper bytes we just show nothing ... IMHO this is the least confusing one. Of course ideally we always know ... |
What about |
@LukasHirt did i get it right, that there are situations where we permanently dont know the folder size? |
That is correct. In oC10 those are mostly related to external storages. When you say calculating - the end user expects this to finish eventually and if it doesn't he will call the help desk = ticket = $100 lost at our customer ... |
|
Oh, I thought it actually becomes available when scan of the external storage is done and synced with file cache 🙈 |
whats learned behavior?Windows File Explorer and MacOS Finder both face (kind of) the same ui-problem. and both display non-semantic information:
(compare screenshots) Applicable for ownCloud Web UI?my guess why they don't show a semantic, more meaningful information like "not available" or "unknown" Suggestion:
Anything I didn't take into account? Windows File Explorer shows nothingMacOS Finder shows "--" Dashes (like dropbox)Suggestion for ownCloud Web UI |
changed #1393 to be |
New folders do not show a size.
Expected behaviour:
Gui elements should not go missing unexpectedly.
New folders should show an indicator when the computation is pending.
Suggestion: Show a '?' where the file size should be. Give explanation about pending, file scan, etc. as a mouse over tooltip.
The text was updated successfully, but these errors were encountered: