neumarcx commented on PR #2123: URL: https://github.com/apache/jena/pull/2123#issuecomment-1845022372
> Hi @neumarcx ! > > +1 for "Upload status"! > > > how about the following mockup. "Success" and / or "Failure" may actually not need to be shown prior to the upload. > > My first prototype didn't show the status by default, then I realized it would "move things in the UI". That's considered bad for UX [1](#user-content-fn-1-0a2d933431e1bda521c96cf9c0e0b774), but more importantly can impact performance negatively [2](#user-content-fn-2-0a2d933431e1bda521c96cf9c0e0b774), so it'd be nice if we could find a permanent place that doesn't move things too much. > > And I didn't use colors because the red would attract your eyes (at least it does to me when I open a page like that), even if it says 0 (imagine Twitter with the notification symbol enabled by default showing 0, or GitHub's notification icon). So instead of users slowly reading the page, their first eye scanning would be to look at the red, and then proceed to use the page[3](#user-content-fn-3-0a2d933431e1bda521c96cf9c0e0b774). Green would have the same effect, and it has also color-blindness issues [4](#user-content-fn-4-0a2d933431e1bda521c96cf9c0e0b774). > > I tried to place each number in a fixed location using table columns so users would know where to find them, once they learn it. But a single line without a table could work too. > > What do you think? Maybe something like your prototype but with the text only? Any thoughts @afs, @rvesse ? > > ## Footnotes > 1. that's CLS, and I hate it because some sites (Twitter, DeviantArt, ...) and apps (Zoom, Discord) have this, that when you have your mouse over a button and something happens and the DOM elements shift, and you end up clicking on something else: https://javascript.plainenglish.io/3-ways-to-fix-cumulative-layout-shift-53df8bea1e0f?gi=e99977032785 [↩](#user-content-fnref-1-0a2d933431e1bda521c96cf9c0e0b774) > 2. because it moves other HTML DOM elements, which might cause JS to have to re-render code like Vue.js components, and redraw things [↩](#user-content-fnref-2-0a2d933431e1bda521c96cf9c0e0b774) > 3. related to visual weight & visual direction: https://www.smashingmagazine.com/2014/12/design-principles-visual-weight-direction/#visual-weight [↩](#user-content-fnref-3-0a2d933431e1bda521c96cf9c0e0b774) > 4. https://www.smashingmagazine.com/2016/06/improving-color-accessibility-for-color-blind-users/#6-color-combinations [↩](#user-content-fnref-4-0a2d933431e1bda521c96cf9c0e0b774) Thank you for the comprehensive motivation for you choices and I can follow your position on my idea with the references. I also see you point with regards to the Cumulative Layout Shift. I don't have an immediate opinion on it but can intuitively sense the issue. The UI might even feel broken as the user might misread the design. Could you please elaborate the one liner idea? May main concern with the multi functional table columns was that they indicate more functionality than is never used. I may have miss interpreted how the status table works. Will the table expand with multiple errors or always it always be juts one line? One table header row and one table value row? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
