UX changes #1650
No reviewers
Labels
No labels
accessibility
app-parity
area: creator
area: daemon
area: design
area: devops
area: discovery
area: docs
area: installer
area: internal
area: livestream
area: performance
area: proposal
area: reposts
area: rewards
area: search
area: security
area: subscriptions
area: sync
area: ux
area: viewer
area: wallet
BEAMER
channel
comments
community PR
consider soon
core team
css
dependencies
electron
Epic
feature request
first-timers-only
good first issue
hacktoberfest
help wanted
hub-dependent
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
merge when green
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
notifications
odysee
on hold
playlists
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
recsys
redesign
regression
resilience
sdk dependent
Tom's Wishlist
trending
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-desktop#1650
Loading…
Reference in a new issue
No description provided.
Delete branch "ux-fixes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Changes
FileList
component, that was when we had the search modal.Images
@tzarebczan a quick test on this would be great
This is my feedback on the code itself, feedback on UI coming separately.
first check no longer adds anything, this can just check for
tooltipText
Not a blocker, but it'd probably be superior if tooltip could be a property of a button, rather than a component that wraps a button.
@ -71,3 +86,4 @@
}
}
}
The margins on
<main>
appear to make this safe for realistic use cases, but what would happen if a tooltip is on a button with a width that would extend past the canvas size?@seanyesmunt there's also a growing number of instances where components are being passed flags that effectively require them to know about what's outside of them rather than operate independently. E.g.
onModal
,onComponent
. We ought to avoid this pattern whenever possible.And here's my UX/UI feedback:
form-row
in an inappropriate manner.Ooh that's a good idea.
@ -71,3 +86,4 @@
}
}
}
Tooltips can extend past the margin with no issues