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

Breakpoint response to style.css text-align overrides #268

Open
RightsandWrongsgit opened this issue Feb 20, 2023 · 0 comments
Open

Breakpoint response to style.css text-align overrides #268

RightsandWrongsgit opened this issue Feb 20, 2023 · 0 comments

Comments

@RightsandWrongsgit
Copy link

I have been very successfully using 'Minimal' as a remote theme that I customize selectively with my local style.css and host on github pages. The primary purpose is for user documentation and as such I frequently call out snippets of code for people to copy and run. There is one aspect of the style.css that doesn't seem to be working as expected and that is around 'text-align' under what appear to be breakpoints in the parent theme. I can inspect the code and see it functioning on its targets and I can localize those targets with increasingly unique css syntax overrides. Where I am having an issue is with an extremely long code block like this bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" that even with a xx-small font-size at 9 point, will do a line wrap. At the classic

level I am running text-align: justify but for the code blocks I am using text-align: left and am 0.5em padding the background with a color that show through the dark-mode I have the full site set to. Where I am getting issues is that the code spilling to two lines, the background spreads broad width and the text acts as if 'justified' rather than 'left' aligned. As I slide past the breakpoints to fit a line full width it does 'left' justify. I am getting differing responses on very narrow breakpoints, mid, and wide breakpoints. I don't see where or how the breakpoints themselves are being set nor how to address the behavior.

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

No branches or pull requests

1 participant