Exporting a file to HTML will always lack title.
If you set a title in the documents properties, then the HTML-document will have this as content of the <title> element. If you leave this document property empty, then the HTML-document will have an empty <title> element, but it exists. If you export your document to XHTML and you do not provide a title in the document properties, an ersatz <title xml:lang="en-US">- no title specified</title> is written. We might consider to write this ersatz text in case of HTML too. But because it is a user error, if he does not specify a title, I consider this lowest importance.
That's a really horrible and confusing user experience. The document properties aren't even exposed sufficiently. Surely if a user sets a style as title, that should set the title in the document properties? While I accept that it's user error and thus of the lowest importance, it's most certainly the fault of poor user experience design.
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Paul, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I confirm the behaviour described by Regina Henschel in Comment 1 using LibreOffice Writer 7.1.4.2 on OpenSUSE 15.2: Version: 7.1.4.2 / LibreOffice Community Build ID: 10(Build:2) CPU threads: 8; OS: Linux 5.5; UI render: default; VCL: kf5 Locale: en-GB (en_GB.utf8); UI: en-GB Calc: threaded Note that the accessibility checker in LibreOffice Writer 7.x checks whether the Title property has been filled in ("Document title is not set") but remains silent when the Title property contains only white space (see the newly submitted Bug 149115). Paul's suggestion to fill in the Title property when the author marks a span of text with the Title style makes sense. However, Writer should then warn the user when: 1. the Title property has already been set; and 2. another part of the document has already been marked with the Title style. The Accessibility Checker currently runs automatically when a document is exported to PDF (assuming the checker has bee enabled in the LibreOffice options). When it is more mature, it should also run when saving a document as HTML or exporting it as XHTML.
Based on above discussion, it sounds like this is not a bug, so I have changed it to an enhancement. In my opinion, it should be of medium priority instead of lowest, but I do not have ability to change that.