-
Notifications
You must be signed in to change notification settings - Fork 827
Improved handling for long words (#155) #171
Improved handling for long words (#155) #171
Conversation
@vanwykjd Nice, I'll have a look at this when i get some free time this week 🙂 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've looked at your changes and they are working pretty nicely. However, I think that we can achieve the same effect just by doing some simple css changes 🙂
Have a look at the following css changes/additions:
.word {
/* Use flex instead of grid */
display: flex;
}
.word__char {
/* Add the width property */
width: 50px;
}
@ollelauribostrom Thanks for looking into my changes and I appreciate your feedback! This isn't the first time I've been guilty of over-analyzing a situation... As you mentioned, I agree that some simple CSS changes should do the trick, and will look into making those changes tomorrow. |
240b576
to
3d9a0bf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For now I think we don't want to introduce to much change to the mobile appearance. It would be sufficient to just add the following css to the existing mobile/tablet media queries:
.word {
display: grid;
grid-template-columns: repeat(auto-fit, 50px);
}
.word__char {
width: auto;
}
@ollelauribostrom I had a feeling the added breakpoints may have been a little much... I tend to get caught up it in the details once I've envisioned something. I changed back to original the media queries and made the adjustments as suggested, but the appearance of the long words revert back to the original issue: (for the mobile devices) My question is whether or not the improvements requested for this issue (#155) regards all devices or just the large, and have the improvements be addressed for the mobile devices in issue #152? |
3d9a0bf
to
c427216
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, I commented on some minor stuff that needs to be fixed before merging this 🙂
src/css/main.css
Outdated
} | ||
|
||
.word__char { | ||
height: 50px; | ||
width: 100%; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can just use width: 50px
(no need for the max-width property as far as I understand 🙂 )
src/css/main.css
Outdated
} | ||
|
||
.word__char { | ||
height: 50px; | ||
width: 100%; | ||
max-width: 50px; | ||
margin: auto 0; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need for this margin property
src/css/main.css
Outdated
@@ -162,7 +165,6 @@ body, | |||
grid-column-start: 1; | |||
grid-column-end: 6; | |||
border: none; | |||
background: #9c0629; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should not be removed since it fixes the progress-bar appearance in FF
57c4a62
to
ae56310
Compare
Nice, thanks a lot 👍 |
Associated Issue: #155
Summary of Changes