Copy link to clipboard
Copied
I was notified by Google about a Mobile Usability Issue for my RH 2017 project (Responsive HTML5 output with Indigo Layout) because viewport tag is not set (for all pages).
If I navigate the TOC, each page is correctly open with the viewport tag set
Copy link to clipboard
Copied
There's no automatic way in RH I can think of. You could try adding the viewport tag manually in a test topic and see if it solves the problem for you. If it works you could then do a find and replace on the code to insert the tag in every topic
Copy link to clipboard
Copied
Thanks for your answer.
I'm wondering if is it possible to customize RH to open a page always in full context. This would by-pass the problem with viewport tag.
Copy link to clipboard
Copied
I'm wondering if is it possible to customize RH to open a page always in full context.
Do you mean as if it were in a web browser showing the TOC etc? If so in the skin settings you can turn off responsiveness then you lose the benefit of having a responsive skin.
Is the issue causing a real problem or are you just getting a warning about something that isn't causing your users a problem?
Copy link to clipboard
Copied
Hello Peter,
In my RH project, if I right-click on a topic in the TOC and select "new tab", the topic is opened in full screen without the side bar with TOC. However, in the header I see " Click here to see this page in full context" and if I click, the side bar with the TOC appears.
So, I'm wondering if I can set my RH project to always opens topics in full context even in new tabs. This shouldn't affect responsiveness.
Copy link to clipboard
Copied
I don't believe that is possible in 2017 as that would effectively require a call that opens the topic via the start page, which is not possible from a right click.
In 2019 New UI there is a frameless output works the way you want but that would require an upgrade and there is a learning curve as the UI has changed completely.
Copy link to clipboard
Copied
Hi Peter,
thanks for your reply.
I guess the issue raised by Google shouldn't cause real problems to the mobile users.