User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Build Identifier: Version 5.2.1.2 Build ID 31dd62db80d4e60af04904455ec9c9219178d620 Help documentation says that Format-->Page has a Background tab from which one can control Background Graphic and Text (= Watermark). This Background tab does not exist. Nor are Watermarks accessible or removable from anywhere else. Reproducible: Always Steps to Reproduce: 1. Open a .docx or other compatible document that has a Watermark 2. Select Format-->Page 3. Look for Background tab, which will not be present Actual Results: There is no tab from which to select Watermark creation, insertion or removal Expected Results: It should have brought up a Background tab which presents a choice of Graphic or Text, according to the documentation. I tried this in Chrome and Firefox browsers--predictably, the results were identical. Reset User Profile?No
Could you link the help page that says that? It's true that the background can be set in a different place: https://help.libreoffice.org/Writer/Changing_Page_Backgrounds Therefore the help page where this is described wrongly has to be changed.
(In reply to Louise B from comment #0) > 2. Select Format-->Page > 3. Look for Background tab, which will not be present > Actual Results: > There is no tab from which to select Watermark creation, insertion or removal > > Expected Results: > It should have brought up a Background tab which presents a choice of > Graphic or Text, according to the documentation. The 'background' tab was renamed to 'area' since v4.4.
The Help page I found that needs changing is vnd.sun.star.help://shared/text/shared/guide/background.xhp?Language=en-US&System=WIN&UseDB=no&DbPAR=swriter It is titled Watermarks. I did try to access this using the Area tab but in that has no option for text in the background (nor for a graphic). Area is not a full replacement for the Background tab as described in that page of the Help.
*** This bug has been marked as a duplicate of bug 96496 ***