-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
fix(docs-infra): set th
/td
to proper width
#35437
Conversation
You can preview 610a750 at https://pr35437-610a750.ngbuilds.io/. |
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.
Good catch!
a86d8d1
to
916fb4f
Compare
You can preview 916fb4f at https://pr35437-916fb4f.ngbuilds.io/. |
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.
Thx for making the changes, @sonukapoor! Can you also change the commit message type/scope to fix(docs-infra): ...
?
Previously, the tables on the event page were misaligned. This commit fixes this by setting the width of all `td`'s and `th`'s.
916fb4f
to
874b0f4
Compare
You can preview 874b0f4 at https://pr35437-874b0f4.ngbuilds.io/. |
th
and last td
in events table
th
/td
to proper width
Co-Authored-By: George Kalpakas <kalpakas.g@gmail.com>
You can preview e6991f3 at https://pr35437-e6991f3.ngbuilds.io/. |
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.
👌
Previously, the tables on the event page were misaligned. This commit fixes this by setting the width of all `td`'s and `th`'s. PR Close #35437
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior?
Does this PR introduce a breaking change?
Other information