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 .
×
Create a free account

Custom character sheet CSS acting funny

So, my group uses a custom version of the old Pathfinder 1e sheet, from when the official sheet sources were available for sheet creators. The problem I am having, I have come to realize, seems to come down to this: Some of the CSS appears to be changing between the CSS submitted in the settings and the result. This difference has occurred since Monday night, ~8:30 PM EDT on the 17th, I believe, as that was our last session and I certainly didn't notice the issue then, nor did anyone else make note of it. Essentially, certain elements are no longer in the positions they should be. I originally assumed that something had changed with the root HTML font size, and in fact changing that in the Chrome developer tools from 10px to 16px did appear to solve the issue. However, as I could not fix that, I chose to see if I could instead change the CSS to work again. In looking at the CSS involved in the positioning and spacing of the elements, I noticed ANOTHER potential cause, as the values in the CSS document are different from those that the Chrome developer tools are showing. Changing these to match the CSS also fixed the issue (and I believe is possibly the true issue). It should be noted, the parts affected by this issue are not aspects I changed or added, but were part of the original sheet and remained unchanged by me. Additionally, I had another member of our group check things, and they saw the same issue (using Firefox browser). The relevant CSS is: .sheet-lab.sheet-under {   position: absolute;   top: 2.4rem;   left: 0; } .sheet-labunder {   margin-bottom: 1.8rem; } And Chrome's developer tools show these values instead: Image of what it should look like vs. what it currently does: vs. The first of these two was achieved by altering the values in the Chrome developer tool to match what the CSS shows. There is no other CSS or style tag in the HTML that is be interfering, and again, this issue did not exist until after Monday, and I have not altered the sheet since then except in my attempts to figure out this issue. I will note again as well that changing the html font-size from 10px to the standard 16px also resolved the issue, but I cannot actually cause that change from within the sheet itself, so that point is moot.   Additionally, the issue appears in multiple places throughout the sheet, but those fixes solve it for all of them, so I don't feel additional examples of it are necessary.
1689895868

Edited 1689895900
vÍnce
Pro
Sheet Author
I think roll20 did some changes to their base.css yesterday (specifically font-size).  I think anything that uses rem units would also be affected by this.  I believe that roll20 either rolled back the change or made an adjustment after numerous issues were raised on the forums.  Are you still seeing a layout issue?
I did not even notice the issue until earlier today (I had not been in that Roll20 game since Monday night's game), maybe an hour before I posted.
1689898581
vÍnce
Pro
Sheet Author
It is odd that the css class has a different value in the inspector.  I don't think I've ever seen that.  Specificity overriding a style, yes, but not changing the actual values.  Is it possible the class has been entered in multiple places on the css sheet?
That's one of the things I checked for, also checked to be sure the style wasn't set inside the HTML. That is the only place it is defined, at all.
1689909746
vÍnce
Pro
Sheet Author
Maybe try adding ".charsheet" to those classes and see if they maintain their values.  I usually do this to all of my classes just to help override roll20's defaults.
That did not resolve the issue, sadly.
1689974859
vÍnce
Pro
Sheet Author
Might be time to submit a help ticket and see what the Devs have to say...