Hi Sumi, Thank you for the feeback! As it is not crystal clear for us what you refer to by There is a vertical scroll and the height grows as the user scrolls down. to investigate this, we need you to contact us on our official support email address - support@oxygenxml.com - and please attach a smal...

Hi Dan, Thank you for your feedback! We already have an issue logged in our internal issue tracking system, so I have just added your vote for this. The interal reference of the issue is "WH-2420". We will notify this thread once a different implementation will be available in a future rel...

Hi Dan02,

I've added your vote and gave the issue we have logged in our system a bump.

Thank you and regards,
Costin

Hi Matt,

To run the WebHelp transformation scenario using the Oxygen GUI software (Editor/Author), you need to have a license for that specific product.

Regards,
Costin

Hi Dan, As WebHelp topics in the output are in fact HTML files, it is possible to style most of the elements appearing in the WebHelp Responsive output through your own CSS customization. In this case, as the Copy button has a dedicated class set on it ("class=copyTooltip"), you could use ...

Hi Matt,

Could you please fist let us know where exactly do you need to impose the restrictions?
Do you need to restrict editing the topics content, or to restrict access to some of the HTML files resulted for their corresponding topic references in the published output?

Regards,
Costin

Hello,

Unfortunately, there is no progress so far and it seems there are no plans to include this feature in the close future, as it is considered only for the long term development.
We will notify this thread when / if this feature will get implemented.

Best Regards,
Costin

Hello, Indeed, in the current implementation of WebHelp, the "webhelp.pdf.link.url" allows a single value, so it is not possible to refer multiple PDF documents. However, even if there is no predefined support for this, we already have a customization example to add a custom component and ...

Hi Greg, Indeed, this is how the links to content in another topic is represented in the current implementation of the WebHelp output - through pernalinks. However, even if there is no out-of-the-box support for removing those from the output, this could be easily achieved through CSS, so you should...

Hi Jonathan, Indeed, the current implementation of Oxygen XML WebHelp always displays the main (index.html) page first and I'm afraid there is no simple way we could think about, so we could not offer a workaround for this for the time being. However, we have an improvement request already logged in...

Hi , Unfortunately we do not have a solution for this. as there is no special place where you could change this.. We suggest you should not try to change any default resources, because this could generate compatibility issues, as the resources from the current version of Oxygen XML WebHelp may no lo...

Hi jmichaels,, As we are not aware of such issues, are you perchance using a custom publishing template? If you are using a custom template, could you please try using one of the default templates and see if it the hangs/freezes still reproduce? If it does, could you please provide a sample where th...

Hi Anna, You can find the version of Oxygen that was used to generate the WebHelp Classic documentation if you either use the Internet browser's CSS inspector to inspect the elements from any topic page in the output, or if you use the context menu action "View page source", on any page fr...

Hi, You could achieve this using a CSS customization of your own. More specific, you could use a CSS selector to match the element that holds your image, then apply your own CSS rules for it, to style the output as desired. You can find detailed information on how to use the internet explorer's CSS ...

Hi Ken. We do not have an out-of-the-box solution for what you want to achieve. Even so, the "toc.xml" file - which represents the basics for generating the TOC - is already present in the temp directory of the output. Given this, most probably you could use it to create your own XSLT exte...

Hi Ken, We used a separate TOC files structure in the past for deprecated transformations, but came to the conclusion it could generate other issues (like security, search related issues, etc.). Thank you for the feedback anyway! Indeed, in the WebHelp implementation we decided to use, there is a mi...

Hi daryl, The Index page should be automatically generated, as long as you have index terms in your publication (use <indexterm> elements in your DITA sources). More details on <indexterm> elementes and how they could be used are available in the DITA specification from this section of our website. ...

Hi, Thank you for the feedback your provided! I've just logged it in our internal improvements system, so that our developers will analyze it and see if there is something we could implement to improve this behavior. Meanwhile, I suggest you should avoid modifying any of the plugin's source files di...

Hi jdupont,

I've just added your vote for it in our system.

We will notify this thread when this will be fixed.

Regards,
Costin

Hi toolie, There is a dedicated parameter which is used to present images displayed at a smaller dimension than the original size in a modal preview. The parameter is called " webhelp.show.full.size.image ", so you could set it to "no" in the parameters tab of the WebHelp Respons...

Hi guibertGE,

We already have an improvement request logged in our internal system and it is currently work in progress.
The new implementation will be included in a future release, so we will notify this thread when this will occur.

Regards,
Costin

Hi, Do you need to remove the form control that presents the "modification" versioning element from editing (while working on the document in the visual Author editing mode from Oxygen)? Out of the box, neither the WebHelp Responsive, nor the PDF based on HTML and CSS transformation scenar...

Hi Ian, I also replied to the email you sent us on our official support email, but just to update this thread, I will also post my reply here as well. There is no out-of-the-box support it in the current implementation of WebHelp. However, we already have an improvement request logged in our interna...

Hello, I'm following this up just to update the thread. By default, all links associated with an an image map open in the same page. However, as a colleague already replied to you on the email support., we have a publishing template customization, which allows you to open those image map links in a ...

Hi revaljilji, Unfortunately this is not possible using the current implementation of the WebHelp plugin. However, we already have an improvement request logged in our internal tracking system, so I've just added your vote for it and we will notify this thread when / if this will get implemented. Re...

Hi Alice, The enlargement works only for the images whose resolution is downsized. More specific, for images displayed at their initial size, there won't be any enlargement pop-up. If you need that behavior for specific images, you should downsize them, using either the " scale " attribute...

Hello,

Unfortunately, the current implementation of WebHelp does not support localizing of custom Javascript modal popovers.

Regards,
Costin

Hi Daryl, There is predefined support for syntax-highlight for codeblocks, so, depending on the value of the outputclass attribute set for each specific codeblock to specify the code/languaget, the corresponding syntax-higlight coloring scheme would be applied over the codeblock's content. You can f...

Hi Christina, There is no out-of-the-box support for the dataLayercript, but you could probably make use of the WebHelp HTML conent insertion capability to use your own Java scripts. There is the How to Insert HTML Content section in the User-Guide that describes how you could add custom HTML conten...

Hi Mark, We could not reproduce the issue on our side, on the latest version 23. Please try using the default WebHelp Responsive transformation scenario, clear of any customization and a fresh copy of oXygen XML that use its own bundled DITA-OT for transformations. You could try testing on the versi...