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

Prevent interactive terms from being on multiple lines of text? #295

Open
MeemawHustlin opened this issue Jan 23, 2023 · 3 comments
Open
Assignees
Labels
formatting/UI Formatting/view changes

Comments

@MeemawHustlin
Copy link
Collaborator

Often interactive terms get split across the end of one line and the beginning of another, resulting in a slightly confusing appearance. Would it be worth it to force these terms to be all on one line? I'm imagining situations like a save file input box being on the line after the name of the save where a player might miss it or be confused not realizing the box is connected to the save name. This could also have a bad outcome of guide text looking very disjointed though.

@MeemawHustlin MeemawHustlin added the formatting/UI Formatting/view changes label Jan 23, 2023
@MichaelEbert
Copy link
Owner

sure? a cursory look through v3 doesn't seem so bad, so either way i think its fine. If you want to add it to the css, go ahead.

@MeemawHustlin
Copy link
Collaborator Author

.item, .spellname, .save { white-space: nowrap; }

does what I want aside from adding a scroll bar to the section. A min width may solve this but an obnoxiously long book name will ruin everything regardless. If I can situationally change the white-space to be nowrap unless the container is too thin, that might work but that'll be much easier to implement after draft PR #298 is done.

@MeemawHustlin MeemawHustlin self-assigned this Jan 25, 2023
@MichaelEbert
Copy link
Owner

can probably simplify to .item .spellname. All saves are items.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
formatting/UI Formatting/view changes
Projects
None yet
Development

No branches or pull requests

2 participants