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
What we're after:
We'd like to include a bit of padding into elements like the Org Chart, reporting examples, the internal button and the external button, since those elements are often followed by other things like texts or images. Right now we can do workarounds using in-line styles in the html, or adding carriage returns in a paragraph block, but it would be good to build this padding into the elements.
JonellaCulmer
changed the title
Org Chart, reporting examples and internal/external buttons need a little bit of padding
Org Chart, reporting examples and internal/external buttons need a little bit of spacing
Nov 19, 2019
@dorothyyeager, Can you include a link to Reporting examples (or other )pages where this issue exists. I had trouble navigating (or searching )my way back to reporting example pages
Summary
What we're after:
We'd like to include a bit of padding into elements like the Org Chart, reporting examples, the internal button and the external button, since those elements are often followed by other things like texts or images. Right now we can do workarounds using in-line styles in the html, or adding carriage returns in a paragraph block, but it would be good to build this padding into the elements.
Related issues
Screenshots
Internal button (external button and reporting examples do the same thing)
As rendered:
Our current workaround: Hit carriage return in the first line of the text block to add the space.
Current html for org chart (in html block, followed by second html block with footnotes):
Current workaround: Inserting this styling into the HTML for the chart:
ul id="fec-orgchart" style="padding-bottom: 2rem;">
Completion criteria
Future work
After the new styling is deployed to prod, we may need to take out a bunch of extra carriage returns, etc.
The text was updated successfully, but these errors were encountered: