-
Notifications
You must be signed in to change notification settings - Fork 32
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
Make slugfield scrollable #1991
Conversation
Code Climate has analyzed commit e97bc26 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 74.8% (0.0% change). View more on Code Climate. |
Thank you for PR 👍 I guess the issue number mensioned in the PR description is not correct... |
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.
Thanks a lot, this fixes the issue! 👍
Could you add a changelog entry for this?
If the slug itself is longer than the input field, we have a "stacked" scrolling now, I was wondering whether we could combine this, so that the input field automatically grows when longer slugs are entered so we only have one layer of scrolling, but I can imagine this is probably a bit complicated, so only improve this if it doesn't cost you too much time 😅
I'm already happy with the current solution! 👍
I guess the issue number mensioned in the PR description is not correct...
True, I fixed it
Oh, and just a minor addition to my comment: So I would use e.g. the following commit message instead:
|
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.
LGTM, thanks!
Yes, that is not possible without using JS/TypeScript magic that might act differently for different browsers, and since it would add probably quite a bunch of complexity and we don't have a very clear structure where this logic resides and how it is tested, if at all (at least that we know of), Ingo strongly favoured not investing more time, and I agree. I would have ideas how to hack it, though. |
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.
Ingo strongly favoured not investing more time, and I agree.
Sounds reasonable! Yes, this leaves us with the changelog entry and the commit message.
- Make slugfield scrollable by setting `overflow: auto` on the container - Ensure `input` is never at 0 width - Reduce label opacity to 60% for better distinction from input Co-authored-by: Gaston69 <ingo@von-komorowski.name>
ecd0350
to
e97bc26
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.
👍
Short description
Make slugfield usable, even if URI prefix is very long.
Proposed changes
overflow: auto
on the containerinput
is never at 0 widthSide effects
.slug-field
will be affected. We estimate this to be fine.Resolved issues
Fixes: #1552 (Slug field layout broken when permalink is too long)
Pull Request Review Guidelines