Bug 863439 - Web branded html output only shows draft watermark on front matter.
Summary: Web branded html output only shows draft watermark on front matter.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ruediger Landmann
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-05 13:34 UTC by Stephen Gordon
Modified: 2016-08-16 01:27 UTC (History)
3 users (show)

Fixed In Version: 3.2.0
Clone Of:
Environment:
Last Closed: 2013-08-09 04:49:35 UTC
Embargoed:


Attachments (Terms of Use)
Screenshot of issue with watermark. (12.87 KB, image/png)
2012-10-05 13:34 UTC, Stephen Gordon
no flags Details

Description Stephen Gordon 2012-10-05 13:34:28 UTC
Created attachment 622175 [details]
Screenshot of issue with watermark.

Description of problem:

When brewing 3.1-Beta versions of the RHEV Installation Guide with book status="draft" I noticed on the stage that the draft watermark only appears properly on the front matter (basically just the TOC page) of the html output.

On subsequent pages the watermark appears to drop into the background behind the white box that constitutes the page. I've attached a screenshot of the top of a page to illustrate what I mean.

I had a look at a local build and the watermark appears correctly so I think this is an issue specifically with the web brand?

Version-Release number of selected component (if applicable):

These are my locally installed packages, not sure if this matters as much versus whatever is in use on the brew hosts for this issue:

publican-common-web-3.0-0.fc17.t216.noarch
publican-redhat-2.99-4.fc17.noarch
publican-3.0-0.fc17.t216.noarch


Additional info:

I checked html-single output on the stage and it looks fine all the way through (draft watermark appears on page throughout the output).

Comment 1 Ruediger Landmann 2012-11-27 00:16:17 UTC
Verified this is still an issue in publican-3.0.0-0.fc17.noarch

Comment 2 Ruediger Landmann 2013-07-30 02:40:23 UTC
This must have been fixed sometime prior to the current development head in Publican itself; will close this with the 3.2 bugs after that release.

Comment 3 Jeff Fearn 🐞 2013-08-09 04:49:35 UTC
The fix for this bug has been shipped in publican 3.2.0


Note You need to log in before you can comment on or make changes to this bug.