Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tourniquets Text Over 20VW to Fix Table Length Issue #1692

Merged
merged 3 commits into from
Jun 27, 2018

Conversation

QuirkyRobots
Copy link
Contributor

@QuirkyRobots QuirkyRobots commented Jun 26, 2018

Fixes table length issue #1690

BEFORE

image

AFTER

image

Using 400px still breaks if at minimum width. However, using Viewport Width (vw) makes it responsive, thus it works at all sizes without out the need for condition media queries.
@QuirkyRobots QuirkyRobots changed the title Tourniquets Text Over 400px to Fix Table Length Issue Tourniquets Text Over 20VH to Fix Table Length Issue Jun 26, 2018
Over VW Comment Change
@QuirkyRobots QuirkyRobots changed the title Tourniquets Text Over 20VH to Fix Table Length Issue Tourniquets Text Over 20VW to Fix Table Length Issue Jun 26, 2018
@QuirkyRobots
Copy link
Contributor Author

QuirkyRobots commented Jun 26, 2018

Using Viewport Width (vw) makes it responsive, thus it works at all sizes without out the need for conditional media queries.

QuirkyRobots added a commit to QuirkyRobots/lbry-app that referenced this pull request Jun 26, 2018
@neb-b
Copy link

neb-b commented Jun 27, 2018

This is great.

@neb-b neb-b merged commit f0f9894 into lbryio:master Jun 27, 2018
@QuirkyRobots QuirkyRobots deleted the patch-1 branch June 27, 2018 05:54
@QuirkyRobots
Copy link
Contributor Author

QuirkyRobots commented Jun 27, 2018

Thanks @seanyesmunt I was looking for it to auto tourniquet based on the current %width, but it would only work with a set VW (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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants