Page 1 of 1

WebHelp Responsive – Custom CSS rules not applied after upgrade to Oxygen 27.1

Posted: Mon Aug 04, 2025 6:18 pm
by natalia_carrilo
Dear support team,
After upgrading from Oxygen XML Editor v25 to v27.1, I’ve encountered issues with custom CSS in WebHelp Responsive output.
In version 25, I used the args.css parameter to load my custom stylesheet, and everything worked as expected. Now, after the upgrade, only some of the custom CSS rules seem to be applied, while others are ignored — even though the setup appears correct.
Could this be related to changes in the way WebHelp handles custom styling or templates in the newer versions? Are there any specific recommendations for ensuring that all custom styles are consistently applied in version 27.1?

Thanks in advance for your help :D

Re: WebHelp Responsive – Custom CSS rules not applied after upgrade to Oxygen 27.1

Posted: Tue Aug 05, 2025 11:17 am
by julien_lacour
Hello,

Oxygen WebHelp Responsive 27.1 includes a major Bootstrap update, introducing new classes and CSS rules. These changes may have overridden or disabled some of your customizations. Could you please specify which rules are no longer being applied in your output?

Regards,
Julien

Re: WebHelp Responsive – Custom CSS rules not applied after upgrade to Oxygen 27.1

Posted: Tue Aug 05, 2025 11:27 am
by natalia_carrilo
Hi Julien
I noticed some table formatting no longer applies as before. I was able to work around it by using !important in my CSS, but I’m not sure if that’s the best approach. I'm concerned there may be other style changes I haven’t noticed yet.

Re: WebHelp Responsive – Custom CSS rules not applied after upgrade to Oxygen 27.1

Posted: Tue Aug 05, 2025 11:55 am
by julien_lacour
Hello,

If your table formatting includes custom background-color, this is the new Bootstrap rule that can override it:

Code: Select all

.table>:not(caption)>*>* {
  background-color:var(--bs-table-bg);
  ...
}
Instead of using !important you can use the following selector: *[class ~= 'topic/tbody'] *[class ~= 'topic/row'] *[class~='topic/entry']

You can try to inspect your HTML pages in your browser to see if new rules may have change the expected behavior.

Regards,
Julien