Summary: | HTML conversion: fields always shaded | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | ajlittoz <page74010-sf> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | ||
Severity: | normal | CC: | buzea.bogdan, heiko.tietze |
Priority: | medium | Keywords: | filter:html |
Version: | 6.4.6.2 release | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 108799 | ||
Attachments: |
Document with page number field
HTML version of test document |
Description
ajlittoz
2020-10-01 07:51:20 UTC
Created attachment 165990 [details]
HTML version of test document
(In reply to ajlittoz from comment #0) > View>Field Shadings has no effect as expected because it is only a screen > visual clue. I can't confirm this observation. If I disable field shadings, html-file doesn't contain a shading. So I suppose that this is the expected behaviour. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. (In reply to Dieter from comment #2) > Could you please try to reproduce it with the latest version of LibreOffice > from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set > the bug's status to 'NEEDINFO'. I checked with my installed 7.0.3.1. Compared to previous 6.4.6.2, View>Field Shadings determines if generated HTML will have a background for fields. I am not sure this is intended behaviour because fields are routinely used to insert "dynamic" content in continuity with text. Nothing should distract reader's attention. The case is different in a form where it should be made clear where the entry "boxes" are located. But in forms, entry "boxes" are not always fields. Field shadings is a convenient tool for a writer during document design (like Formatting Marks) but is disturbing for a reader of the final document. So it should be explicitly asserted if View>Field Shadings has an editing effect and be consistent with Print Preview where Field Shadings does nothing. I believe Print Preview (and Print for sure) are closer to expected behaviour than saving as HTML. [Automated Action] NeedInfo-To-Unconfirmed (In reply to ajlittoz from comment #3) > (In reply to Dieter from comment #2) > > Could you please try to reproduce it with the latest version of LibreOffice > > from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set > > the bug's status to 'NEEDINFO'. > > I checked with my installed 7.0.3.1. > > Compared to previous 6.4.6.2, View>Field Shadings determines if generated > HTML will have a background for fields. > > I am not sure this is intended behaviour because fields are routinely used > to insert "dynamic" content in continuity with text. Nothing should distract > reader's attention. Let's as design-team, if this is intended behaviour or not cc: Design-Team In both, 6.4 and 7.2 the field remains shaded after export to HTML but the file itself is clean. And I wouldn't expect that any export operation affects the current status. It's similar to a vector graphic that doesn't becomes rasterized when saving as PNG. Version: 6.4.7.2 Build ID: 6.4.7-2 CPU threads: 8; OS: Linux 5.9; UI render: default; VCL: kf5; Locale: de-DE (en_US.UTF-8); UI-Language: en-US Calc: threaded Version: 7.2.0.0.alpha0+ Build ID: 23255d4e09292bc7f4d40993f9fa9156834f160c CPU threads: 8; OS: Linux 5.9; UI render: default; VCL: kf5 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded We discussed the topic in the design meeting * fields don't have a background color but are highlighted per code * there is no good reason to show the internal highlighting when opening the exported html in a browser (Heiko) * exporting to a file shouldn't affect the actual document; same happens in MSO * export doesn't take the highlighting in LibreOffice too but SaveAs does => this is a clearly bug Dear ajlittoz, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug Bug still present with Version: 7.4.3.2 Build ID: 40(Build:2) CPU threads: 4; OS: Linux 6.0; UI render: default; VCL: kf5 (cairo+xcb) Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded |