You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 8, 2019. It is now read-only.
I couldn't get some custom styles to work. Putting them inside styles tags of extent-reports.xml config file didn't work.
After some searching inside this plugin source files I noticed that "styles" doesn't seem to be used. What I found is that "css" is used there. So putting my styles inside "css" config did the trick:
<!-- custom styles -->
<css>
<![CDATA[ <!-- I've put my styles here -->]]>
</css>`
So I report this, so everyone having this issue can solve it.
I can imagine two solutions to this issue. Either having the rest of the plugin read "styles" from config as well or updating reference extent-config.xml file to have "css" section there.
Edit: I forgot to specify version I was using. It was 3.1.3
The text was updated successfully, but these errors were encountered:
Thank you for taking time to research this hook. Version 4 supports both styles and CSS tags - to be backward compatible with version 2 and version 3 config xmls.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I couldn't get some custom styles to work. Putting them inside styles tags of extent-reports.xml config file didn't work.
After some searching inside this plugin source files I noticed that "styles" doesn't seem to be used. What I found is that "css" is used there. So putting my styles inside "css" config did the trick:
So I report this, so everyone having this issue can solve it.
I can imagine two solutions to this issue. Either having the rest of the plugin read "styles" from config as well or updating reference extent-config.xml file to have "css" section there.
Edit: I forgot to specify version I was using. It was 3.1.3
The text was updated successfully, but these errors were encountered: