Tourniquets Text Over 20VW to Fix Table Length Issue #1692
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#1692
Loading…
Reference in a new issue
No description provided.
Delete branch "patch-1"
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?
Fixes table length issue https://github.com/lbryio/lbry-app/issues/1690
BEFORE
AFTER
Using Viewport Width (vw) makes it responsive, thus it works at all sizes without out the need for conditional media queries.
This is great.
Thanks @seanyesmunt I was looking for it to auto tourniquet based on the current
%width
, but it would only work with a setVW
(viewport width).I will spend more time on this at a later date and play around with things like converting the current table % values to VW to see if that is a better solution that will be globally acceptable for any sized area, which I think was @kauffj's concern.
For now, these are a good fix with the current layout.