-
Notifications
You must be signed in to change notification settings - Fork 382
fix(scss): code annotation line highlight overflow #13429
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
base: main
Are you sure you want to change the base?
fix(scss): code annotation line highlight overflow #13429
Conversation
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) ✅ license/snyk check is complete. No issues have been found. (View Details) |
This is a CSS change. CSS changes are scary, and we need stronger assurances of the before-after behavior; we don't have good regression protection here. Have you tested the following?
|
Thanks for the screenshots! They are very encouraging.
If that's the case, then we should be treating this as a regression, and hotfix 1.8. Do I understand this right? |
Let me check if my guess is correct by testing on 1.7 first. |
The line highlighting is working properly in 1.7, so that's indeed a regression. |
So basically the change is removing these rules margin-left: -4em;
width: calc(100% + 4em); and using the same as the It looks scary to have this impact, and it raises a question for me about the underlying DOM change—as if Also I am seeing those rules are set in revealjs too... Is it impacted too? quarto-cli/src/resources/formats/revealjs/quarto.scss Lines 772 to 787 in 9272aaa
is this the change with the scafold for code copy button that impact this? Sorry for all those question - this just warns in my head when I see CSS fix only - always wondered if we missed something in our after body processing that does post process in client or in our HTML post processor... hard to know... 🤔 |
Removing the CSS rules for:
The div of class Leads to a better display (no bump): |
If I remove all the "gutter" pieces, the brute-force way, including from the JavaScript script: Screen.Recording.2025-09-26.at.19.26.39.movThis breaks code-annotation for Reveal.js, so let's not do that without finesse. I think an in-depth follow up on the copy-button change is really needed as many things are not right now regarding code blocks/cells. |
Let's do our best to be concrete here: "many things" and "not right" are not helpful terms to get us from here to there. |
I can compile a list or what I'v seen and are clear visual regression that cannot possibly be considered as anything other than a bug. edit: the regression from 1.7 I remember how to reproduce: |
Adjust the CSS for code annotation line highlights to prevent overflow issues, ensuring proper display and alignment.