Summary: | FILEOPEN: DOC: Checkbox missing | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Xisco Faulí <xiscofauli> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | l.lunak, miguelangelrv, xiscofauli |
Priority: | medium | Keywords: | bibisected, bisected, filter:doc, regression |
Version: | 4.4 all versions | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 104527 | ||
Attachments: | sample |
Description
Xisco Faulí
2016-12-15 14:19:42 UTC
Regression introduced by: author Luboš Luňák <l.lunak@collabora.com> 2014-11-07 15:14:21 (GMT) committer Luboš Luňák <l.lunak@collabora.com> 2014-11-09 18:44:25 (GMT) commit 6a5dbe73537642b06bcde782118a34b4593d17eb (patch) tree ae6f0d75dde1ab0a8cc524edbad19338ea90ddf0 parent 123e49d6e307c41a5f59878335563ad7203b23ff (diff) do not iterate over all bookmarks in SwTxtNode::Update() 3f9872185e introduced new API for fast finding of marks to a specific text node, so use that (code itself based on cb46aaf2d7). This makes mailmerge faster (since it can create a huge document, and especially with the change to use UNO bookmarks to mark starts of MM documents inside the larger single document there can be a large number of marks). Adding Cc: to Luboš Luňák Hi Xisco, looks like a dup of #87183 m.a.riosv, Bug 87183 is not a regression and was verified in 4.3. This is a regression that was introduced in 4.4. I just tested this bugdoc on master (version 6.0) and it works nicely. Xisco, can you check whether you still reproduce this issue. Otherwise it would be good to close this bug. Yes, it's fixed in master: Version: 6.0.0.0.alpha0+ Build ID: 78960ad06faca055a6d97afbc764c902d5d07f6f CPU threads: 1; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@39, Branch:master, Time: 2017-08-30_06:31:19 Locale: es-ES (es_ES); Calc: group Closing as RESOLVED WORKSFORME and setting backportRequest:5:4 bibisecting suggests that this was fixed on Aug 11ish, but I can't guess which one of those is the fix. |