You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first column in particular, which often contains field names, is too small to fit many of these field names. For example, DiscountedFee gets cut to "Disco / unted / Fee" in this table:
This is something that can be improved (to some extent) with CSS. On xrpl.org, the CSS prioritizes not breaking these field names, so the same table would render like this:
It seems that the main culprit is the following CSS rule:
I'm not sure where this rule is coming from originally (it's one of the "inline" style sheets) but it's usually better not to apply that within tables. There are drawbacks to this—if you have really long field names/code lines in a table then it can distort the table or run it off the side—but they're manageable and legibility is generally better without it in my experience.
The text was updated successfully, but these errors were encountered:
The first column in particular, which often contains field names, is too small to fit many of these field names. For example,
DiscountedFee
gets cut to "Disco / unted / Fee" in this table:This is something that can be improved (to some extent) with CSS. On xrpl.org, the CSS prioritizes not breaking these field names, so the same table would render like this:
It seems that the main culprit is the following CSS rule:
I'm not sure where this rule is coming from originally (it's one of the "inline" style sheets) but it's usually better not to apply that within tables. There are drawbacks to this—if you have really long field names/code lines in a table then it can distort the table or run it off the side—but they're manageable and legibility is generally better without it in my experience.
The text was updated successfully, but these errors were encountered: