Writer destroys some html

When editing html documents, in Html Source mode, Writer accepts html tags and saves them (for example, for example SPAN tags… But if you switch back to Web Layout mode, and then back to Html Source mode,that html may have been destroyed.

For example:

<span title="We use your personal information only to communicate with you."
      style="color: blue">our privacy policy</span> 

becomes:

<FONT COLOR="#0000ff">our privacy policy</FONT>

I like using Writer to edit html, but this is a problem. Any suggestions for how to get it to preserve custom html?

Thanks

Hi @Alan3,

This sounds like a bug that would qualify as “data loss.” As you might be aware, the LO community takes data loss bugs quite seriously. Please file a bug about this problem. The QA team will be happy to help you track down this issue! Thanks!

Maybe this can help:

Thank you. I’m aware of that.

The problem is that, once you’ve saved the document as .html, and edited some of the html code, if you go then switch back to "Web Layout mode, the editing you did while in html mode may be affected, as in my question: I used html mode to place a SPAN tag around the phrase “our privacy policy”. The SPAN tag had the “Title” attribute set to “We use your personal information only to communicate with you.”. Hold your mouse over the first instance of “our privacy policy” in my question, or view the source code to see what I mean. Then I switched back to Web Layout mode and made some edits elsewhere in the document. When I previewed the document after saving it, the SPAN tag and its title attribute was gone, replaced by the FONT tag. (Hold your mouse over the second instance of “our privacy policy” in my question, or view the source code to see what I mean.

Hi @Alan3,

This sounds like a bug that would qualify as “data loss.” As you might be aware, the LO community takes data loss bugs quite seriously.

If installing the latest release doesn’t seem to fix this problem, please file a bug and provide a list of steps that can reproduce it. The QA team will be happy to help you track down this issue!

Please post a link to any bugs you file in a comment below using the format “fdo#123456”.

Thanks!