strange printing behaviors for WebHelp topics

[chrispitude]

We found some strange printing behaviors for WebHelp topics. Here is a testcase:

webhelp_print_page.zip

(3.55 KiB) Downloaded 275 times

The project.xml file publishes a topic to html5 and webhelp-responsive, with the following simple CSS applied to both:

Code: Select all

body {
  font-family: Roboto, sans-serif;
  font-size: 14px;
}

.topictitle1,
.wh_topic_content .title.topictitle1 {
  font-size: 2em;
  line-height: 1.1em;
  font-weight: bold;
}

.p {
  line-height: 1.5em;
}

[chrispitude]

In Chrome, the html5 print preview is as follows:

image.png (222.44 KiB) Viewed 2178 times

The webhelp-responsive print preview for a page with no left-side TOC is as follows:

image.png (112.73 KiB) Viewed 2178 times

Somehow the viewport is larger, which scales down the font size in both the content and the headers/footers. In addition, the page itself is a different aspect ratio, which also suggests some kind of change in the viewport.

The webhelp-responsive print preview for a page with a left-side TOC is as follows:

image.png (117.94 KiB) Viewed 2178 times

Now somehow the width allocated to the content has been reduced.

[chrispitude]

In Firefox, the html5 print preview is as follows:

image.png (143.38 KiB) Viewed 2177 times

In Firefox, the webhelp-responsive print preview is the same with or without a left-side TOC:

image.png (65.03 KiB) Viewed 2177 times

The page aspect ratio is still correct, but the viewport has scaled the font size down. And the right-size header is cut off, which also suggests some kind of viewport/scaling issue.

[chrispitude]

I am hoping there are some kind of CSS print directives that can be added to the WebHelp page structure so that the topic content is printed normally without the viewport/scaling issues. Our previous online help tool supported this, although that tool placed all topic content inside an <iframe> so it probably had an easier time partitioning the topic content from the surrounding page structure.

Please let us know the issue ID so we can track it on our side. This issue is not urgent on our side, but it would be nice to see it fixed some day.

[marius]

Hi ,
I've just filled out an issue based on your observations and testcase, with the id: WH-3092
We'll update this thread when we'll have a resolution for this issue.
Best regards,
Marius

[fangwei]

Hi,
Is there any update?

[Costin]

Hello,

As the improvement request was logged recently, there is currently no update.
The status is still "Open" in our internal tracking system. We will notify this thread when an implementation will become available.

Best Regards,
Costin

[fangwei]

Hi,
Would it be possible for you to provide an ETA? It has been two months since the request was created. If we call it "recently", when do we expect a solution? We have tens of thousands of users that are impacted by this. Kindly consider this urgent.

[cosmin_andrei]

Hello,
Thank you for your feedback and we will increase the priority for this issue as this seems to be very important for you.
As this is not planned to be implemented in the near future and we cannot provide an ETA.

[fangwei]

Hi,
Is there an update?

[ionela]

Hi,

I'm really sorry, but currently this issue is not scheduled for implementation.
We'll try to prioritize it for the next version of Oxygen XML.

Regards,
Ionela

[fangwei]

Hi Any update?

[cosmin_andrei]

Hello,
As my colleagues previously specified the improvement request was logged recently, there is currently no update.
The status is still "Open" in our internal tracking system. We will notify you when an implementation will become available.