Columns within a Note do not appear in the correct position
See original GitHub issueSee Reddit thread: Columns within a Note
Columns within a note are appearing in the incorrect position since the change from v2.10.6 to v.2.10.7 Using Chrome’s Inspect Element tool shows the highlighted block in the correct position; however this is not where the text appears.
Investigating the changes included in this version change, it appears that the inclusion of -webkit-transform: translateZ(0);
is what is causing the change in behaviour. This change was originally intended to resolve issue #1179 but the solution has broken any existing columns in blockquotes.
So far, the only solution I’ve been able to find is to remove the -webkit-transform: translateZ(0);
line completely. 😦
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Insert a column break - Microsoft Support
In Word 2013 or Word 2010, click Page Layout > Breaks. A menu with options will appear. Click Column. A column break is...
Read more >Add a table in Notes on Mac - Apple Support
Manage rows and columns In the Notes app on your Mac, click a note in the notes list or double-click a note in...
Read more >10 tips for working with Word columns | TechRepublic
Arranging text and graphics into columns is an effective way to make your document more readable and ... 1: Use the right tool...
Read more >Using and formatting columns in Microsoft Word
Place your cursor after the end of the last column, then go to the Page Layout tab and, under Columns, change it back...
Read more >The strait and narrow: using columns in Word
Word 2010: Go to File | Options | Advanced: Show document content and check the box for “Show text boundaries.” Word 2013 and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For sure, we need to standardize our margins/padding/spacings between elements. We have a lot of “margin-bottom after this element”, but then “negative margin-top for the next element” but then “negative margin for this element ONLY if directly after the first element, but then positive in this other special case.” Lots of conflicting bandaids patched over and over when we really just need one consistent number for most cases.
Closing this as the root issue has been resolved by reverting the relevant commit.