BugFix: Proper arrangement of Nos. in tables

[aayush420]

Fixes the single character wide Nos column to a bit more spacious column.

• From this:

• To this:

[hblankenship]

This is for a particular use case and may not be appropriate for all cases. In addition, the recommendation is to NOT use tables but come up with a different way to present the information. Finally, if you insist on using tables, you may create the necessary style within your index.md page or css folder.

[aayush420]

This is for a particular use case and may not be appropriate for all cases. In addition, the recommendation is to NOT use tables but come up with a different way to present the information. Finally, if you insist on using tables, you may create the necessary style within your index.md page or css folder.

Yeah right. But having a minimum width rule is never a bad thing right? (At least that's what I thought. Please Correct me if I'm wrong...)

[hblankenship]

I think it would depend on the circumstance. If the first column only had 'a' or '1' it may not need 35px. Further, if the next person wants to have 12345 in the first column, 35px would not suffice.

[aayush420]

I think it would depend on the circumstance. If the first column only had 'a' or '1' it may not need 35px. Further, if the next person wants to have 12345 in the first column, 35px would not suffice.

Agreed. And 35px was particularly chosen because of the fact that,... if the content is of

• single character, i., 1-9, or a-z or something similar, it would be covered by text-align:center; property which is also included in the PR.
• 2-4 characters, 35px would cover it anyway.
• 5+ characters like the example you suggested (12345), It would already be heavy on the browser anyway with all those 10k+ rows in the table. At that point, UX barely matters and hence an added row is OK (Just an assumption).

The main motive was to cover the majority of the cases i.e., <1000. And this is covered pretty well by 35.