<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - Bulleted added to heading after copy/paste" href="https://bugs.documentfoundation.org/show_bug.cgi?id=134946#c19">Comment # 19</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - Bulleted added to heading after copy/paste" href="https://bugs.documentfoundation.org/show_bug.cgi?id=134946">bug 134946</a> from <a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>(In reply to Terrence Enger from <a href="show_bug.cgi?id=134946#c18">comment #18</a>) Looking through my own list. Bullets + Track changes is about Track changes not handling bullets properly. (M. Stahl) Bullets and slow is probably Idle/Timer; (Tobias Madl/Meeks) Heading gets bullet means a Heading without bullet gets a bullet. (Inherited) Bulleted list disappearing after paste undo redo is about throwing the bullet list away. So about UNDO-redo code. (M. Stahl) RTF code -> Miklos DOCX -> Miklos/ Justin Bullets and file formats is tricky area. RTF bullet are not per definition a or DOCX bullet. And RTF Special Paste isn't equivalent for Save as RTF. Even a bullet pasted from a DOCX pasted with Special Paste RTF can behave differently. Even worse an DOCX saved to ODT. They ODT inherits all the flaws of the DOCX or DOC. So there a clean ODT files and those based on conversion. Bullet and table is bullet and table.. So seeing not many similarity's. Ideally I prefer bug which can be bibisected.. You know for sure if it's shared. <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Select All cut leaves bullet behind of on top of the page" href="show_bug.cgi?id=135301">Bug 135301</a> and <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - First bullet not included in track changes" href="show_bug.cgi?id=135292">bug 135292</a> are more or less the same different consternation of the same issue. On in general the other specific to track changes. It might be that the track changes variant isn't solved with the 'general' fix.. I might be the case. Another beloved area of me is the anchoring area. There are at minimum two types (maybe even 3) of 'to character' 'to paragraph'. Shape anchor to paragraph is subtle different from image to paragraph.. Which produces quite some fun. Even they DOCX anchor behavior is can be different if imported in LibreOffice. Most page loops (DOCX/DOC/ODT) are image anchoring issues. Long short freezes too. Text layout engine is running over time to position the anchor an fails. Ideally it bails out.. Image on top of text (without wrap). But quite number of cases where this doesn't happen. Anyhow they area there is currently not much to add. Except being flawed. They anchor to paragraph (for images/not shapes) is/was pretty stable.. To character can be problematic, IMHO. But will how it goes.. it's the default since 6.4. Anyhow in that area I may overdo it a little. Except of adding examples to test if someone someday wants to fix they anchoring [they person who touches it will be hunted for years based on my estimation and lots and lots of frustration.] Text page layout so much fun: Timers, footnotes, tables, anchors, text shaping (Harfbuzz) comes together. Footnotes pushing text to different area, triggering shape measurement (Harfbuzz (expensive) and text break (ICU). Different text break trigger anchor movement (so different position of shape). Text must be layouted again around the shape (wrap). Which triggers a footnote movement. Which triggers to table move. Which triggers lay-outing of embedded table. And footnotes starting to move again.. Currently they tables are optimized.. no crashing.. So instead of crashing we opt for looping :-) they table code being stable. So take a short cut.. stop rendering. you end up with tables which shift on clicking :-). Which could also be a timer stopping to soon/late. But, yes, I do not really I'm guilty of not always using search in advance.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>