Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×

CWOD Hunter CSS not rendered

Hi--    My group and I noticed that the CSS for the community CWOD-Hunter sheets isn't being rendered in like the CWOD-Vampire. Looking at it, it seems similar enough, but the style tag is empty. Any hints as to why that might be? I checked the sheet.json, I do see that hunter has a roll20userid field. Could that break it? Do I need to add a translation.json ? Doesn't look like it, but I may try. I'm going to do some cleanup anyway, possibly convert it to a grid CSS, so I thought I'd fix that too. CWOD-Hunter sheet <style type="text/css" title="charsheet"></style> CWOD-Vampire sheet <style type="text/css" title="charsheet">.charsheet label { display: inline-block; width: 93px; text-align: right; padding-bottom: 0px; padding-right: 0px; } </style>
1601039607
GiGs
Pro
Sheet Author
API Scripter
In roll20, you shouldnt be using a style tag like that. You have two files - a html file and a css file. CSS is placed in the css file, and when roll20 loads the sheet both the html and css files are loaded. So, without looking at it, the hunter sheet's style tag is empty because that sheets css is stored in its .css file. You can (and should, honestly) safely delete those style tags.
Yeah, those style tags are from the page source of a popped out character sheet (trying to my example keep it simple), both sheets store their css in a file but one ends up with an empty style tag and the other doesn't. And anyway, style tags belong in the head tag and the html fragments in the repository don't have head tags.
1601054210

Edited 1601054253
Kavini
Pro
Marketplace Creator
Sheet Author
Compendium Curator
From my experience this will likely be that there's some invalid content in the CSS file. For some reason there are certain things that cause Roll20 to out of hand reject a CSS file, for example using the word 'evaluate' as a class name. A quick glance through the code and my hunch is that it would be this line: content: "<p>A Gem: <span style="font-family: 'Pictos Three'">a</span></p>"; Although I can't be certain. I will do some experiments later if nobody has fixed it before then.
1601059091
Andreas J.
Forum Champion
Sheet Author
Translator
Nic B. said: From my experience this will likely be that there's some invalid content in the CSS file. For some reason there are certain things that cause Roll20 to out of hand reject a CSS file, for example using the word 'evaluate' as a class name. A quick glance through the code and my hunch is that it would be this line: content: "<p>A Gem: <span style="font-family: 'Pictos Three'">a</span></p>"; Although I can't be certain. I will do some experiments later if nobody has fixed it before then. What would be the potential problem here? AFAIK, there is no problem using the custom roll20 fonts in character sheets, is it bc it has a style attribute?
📜🗡Andreas J.🏹📜 said: Nic B. said: From my experience this will likely be that there's some invalid content in the CSS file. For some reason there are certain things that cause Roll20 to out of hand reject a CSS file, for example using the word 'evaluate' as a class name. A quick glance through the code and my hunch is that it would be this line: content: "<p>A Gem: <span style="font-family: 'Pictos Three'">a</span></p>"; Although I can't be certain. I will do some experiments later if nobody has fixed it before then. What would be the potential problem here? AFAIK, there is no problem using the custom roll20 fonts in character sheets, is it bc it has a style attribute? I'm guessing that the double quotes inside the content aren't escaped properly, when I corrected that it made my linter happy. I'll add that to the PR I'm gonna do tonight and hopefully it will be fixed before our next game.