-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
doc: fix word wrapping for api stability boxes #14809
Conversation
Is there a reason why these boxes are I'd change them to |
Mostly enjoying the new code line quoting 👐
AFAICT that's the header for each API endpoint: Line 33 in 314217f
Lines 397 to 406 in 314217f
That maps: Lines 678 to 684 in 2e7ccc2
to: Anyway let's do both: replace the markup and the rendering code |
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.
Looking fine to me, thanks.
doc/api_assets/style.css
Outdated
white-space: pre-wrap; | ||
word-wrap: break-word; | ||
padding: 1em; | ||
line-height: 1.5; |
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.
Are these (esp. the font and wrapping ones) still necessary now that the container has been switched to a <div>
?
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.
Ahh, you're right. Since it's not pre
anymore, the wrapping is no longer an issue. The padding
and line-height
are still necessary 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.
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 think I like it more with the extra space. Another option would be to make it a <p>
which already sets 1.5em line-height
and a similar margin-bottom
, so you save two declarations.
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.
Thought, it might be unexpected to have <p>
and those boxes share CSS. So, LGTM as-is.
This reverts commit e0dcbd7.
A bunch of other people are looking at this more closely and with more expertise than I bring to CSS etc. Plus, my review is from a version of this PR that is now several iterations old. Dismissing my review and letting the knowledgable folks handle it instead. Thanks!
doc/api_assets/style.css
Outdated
white-space: pre-wrap; | ||
word-wrap: break-word; | ||
padding: 1em; | ||
line-height: 1.5; |
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.
Thought, it might be unexpected to have <p>
and those boxes share CSS. So, LGTM as-is.
Landed in eab2bea. |
PR-URL: #14809 Fixes: nodejs/nodejs.org#1337 Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Daijiro Wachi <[email protected]> Reviewed-By: Roman Reiss <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
PR-URL: nodejs/node#14809 Fixes: nodejs/nodejs.org#1337 Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Daijiro Wachi <[email protected]> Reviewed-By: Roman Reiss <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
PR-URL: #14809 Fixes: nodejs/nodejs.org#1337 Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Daijiro Wachi <[email protected]> Reviewed-By: Roman Reiss <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
PR-URL: #14809 Fixes: nodejs/nodejs.org#1337 Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Daijiro Wachi <[email protected]> Reviewed-By: Roman Reiss <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
PR-URL: #14809 Fixes: nodejs/nodejs.org#1337 Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Daijiro Wachi <[email protected]> Reviewed-By: Roman Reiss <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
Checklist
Affected core subsystem(s)
doc
This is meant to fix the issue that was opened here originally.
Fixes: nodejs/nodejs.org#1337
Before:
After: