https://bugs.documentfoundation.org/show_bug.cgi?id=170602
--- Comment #1 from Justin L <[email protected]> --- Created attachment 205361 --> https://bugs.documentfoundation.org/attachment.cgi?id=205361&action=edit bookmarkCorrupts_blockSdt.docx: MS Word already considers this document to be corrupt This comment actually describes a situation where LO current works well. It even takes this second corrupt document and round-trips it as a valid document... Surprisingly, content controls that contain a paragraph (blockSdt) are more restrictive in this aspect than are runSdts. <w:sdt> <w:sdtContent> <w:p> w:bookmarkEnd OK up to this point <w:r> w:bookmarkEnd MUST not occur from this point onwards <w:rPr/> <w:t> some content </w:p> </w:r> <w:r> <w:t> ending content </w:p> </w:r> </w:p> w:bookmarkEnd OK from here onwards </w:sdtContent> </w:sdt> P.S. Where the bookmark starts doesn't matter. For example, even if the bookmark starts in the Sdt, it still is not allowed to end in the Sdt. (Microsoft's UI blocks the 'Insert - Bookmark' option while inside a content control). P.P.S. LO tends to avoid this situation often, because it converts blockSdt's into runSdt's (which are more lenient). Once again, these restrictions do not apply to richText or w:group. -- You are receiving this mail because: You are the assignee for the bug.
