Title Bar font is misbehaving in Responsive HTML5 output

[aceinevo]

Please help - this issue is sapping up valuable hours and I can't find a solution. I've created a nice new responsive HTML 5 layout in RoboHelp 11 - however the Title Bar font is not rendering the size as stipulated in the editor.

This seems to be project specific as I can use stock and other Screen Layouts with the same result. I exported my custom Responsive Layout into a new project and it behaved as it should.

The generated result I get (illustrated above) has an incorrect font size in the Title Bar, the point size of this font should be much larger. I've checked through just about every project setting and I have no idea why it is doing this.

Doing the same with the stock Responsive Screen Layout:

Is someone able to shed some light on this, your recommendations would be greatly appreciated.

[Peter Grainge]

I have moved the post to the HTML5 Layouts forum.

---

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

[marielinas]

I had a similar issue in my responsive layout and I tracked it down to hyperlink styling - so do you have styling in your project that defines the font size of hyperlinks by any chance?

[kennethc2]

Does the font size issue happen regardless of which specific page you're on? I had a similar issue with the font color of the title bar and ended up deleting extra styling information in the html of specific project pages.

[Willam van Weelden · Accepted solution]

Do you have the setting 'Limit scope of project styles' enabled in your SSL?

My guess is that this setting is causing the problem.

Kind regards,

Willam

[aceinevo]

Hi - this was a precise fix to the problem. Thank you.

[aceinevo]

This was disabled and enabling it fixed the problem.

[Willam van Weelden]

Good to hear. I would just like to remark that this option should always

be enabled, both for Multiscreen HTML5 and Responsive HTML5. You could

get a lot more weird issues when this is disabled.

Kind regards,

Willam

[aceinevo]

Note to developers - this was disabled by default when creating a new Responsive HTML5 layout. Had it been enabled from start, this could have saved me hours of frustration.

Thanks to Willam for identifying the problem.