-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Markup: rendering edits for 2025 edition & beyond #3623
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?
Conversation
I'm going to complain just a little bit because I should have complained last year, but I don't really like it. They are 5 cells that happen to have the same value, not just a single cell. |
@nicolo-ribaudo That's totally legit. I think it's important to keep in the printable version (it's the only way all the text fits on the page) but I do not feel strongly—at all—about adding it to the web version, aka the actual source of truth. |
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 agree we should back out the colspan
change; we can make some other permanent change later, or just keep applying manual edits to the PDF. Otherwise LGTM.
If the |
If we renamed [[PendingAsyncDependencies]] to [[PendingAsyncDeps]], would it fit? Maybe that could be an option to consider. |
This PR