Character Vault
Any Concept / Any System
Compendium
Your System Come To Life
Roll20 for Android
Streamlined for your Tablet
Roll20 for iPad
Streamlined for your Tablet

Personal tools

Difference between revisions of "Character Sheet Development/Bugs & Quirks"

From Roll20 Wiki

Jump to: navigation, search
m (Bugs)
m (CSE)
Line 17: Line 17:
 
* '''[[Macro_Guide#HTML_replacement|HTML replacement characters]] have been observed to sometimes be converted prematurely''' after the CSE update was made which can cause sheet roll macros to break.
 
* '''[[Macro_Guide#HTML_replacement|HTML replacement characters]] have been observed to sometimes be converted prematurely''' after the CSE update was made which can cause sheet roll macros to break.
 
** Only appears to happen in [[CSE]]-mode. reported by Ayethin & [[Vince]]
 
** Only appears to happen in [[CSE]]-mode. reported by Ayethin & [[Vince]]
 
  
 
* in some cases, <code>.charsheet</code> needs to be added to the CSS classes, which previously worked fine with [[Legacy Sheet]]
 
* in some cases, <code>.charsheet</code> needs to be added to the CSS classes, which previously worked fine with [[Legacy Sheet]]
Line 24: Line 23:
 
** [[Chris D.]] may have uncovered strange behavior with CSS comments using multiple asterisk characters. eg <code>/******/</code>
 
** [[Chris D.]] may have uncovered strange behavior with CSS comments using multiple asterisk characters. eg <code>/******/</code>
 
** [[Scott C.]] notes that this may be an older bug{{source|https://app.roll20.net/forum/permalink/10007760/}} and suggests to use <code>#</code> instead.  eg <code>/*######*/</code>  
 
** [[Scott C.]] notes that this may be an older bug{{source|https://app.roll20.net/forum/permalink/10007760/}} and suggests to use <code>#</code> instead.  eg <code>/*######*/</code>  
 +
* detail & summary element styling is inconsistent between browsers/versions {{fpl|10029180/  details}}
  
 
* '''fixed''' <strike>issues with @import</strike> {{fpl|10024551/ Release Note for April 27, 2021}}
 
* '''fixed''' <strike>issues with @import</strike> {{fpl|10024551/ Release Note for April 27, 2021}}
 
** <strike>if a @import exists, it seems it might result in roll20 ignoring the first instance of the next css class in the file, workaround is to add an empty, "sacrificial" version of the class first that will be eaten up, and the one after will work normally </strike>
 
** <strike>if a @import exists, it seems it might result in roll20 ignoring the first instance of the next css class in the file, workaround is to add an empty, "sacrificial" version of the class first that will be eaten up, and the one after will work normally </strike>
 
 
  
 
==LCS==
 
==LCS==

Revision as of 17:55, 5 May 2021

Main Page: Character Sheet Enhancement


Listing random quirks of the sheet system, especially those related to issues surrounding the CSE rollout and updated code sanitation on Roll20's part.

Contents

Bugs

  • using optgroups in select doesn't work on custom sheets, even though it works on existing sheets like Free Spacer

CSE

Bugs related to CSE.

  • HTML replacement characters have been observed to sometimes be converted prematurely after the CSE update was made which can cause sheet roll macros to break.
    • Only appears to happen in CSE-mode. reported by Ayethin & Vince
  • in some cases, .charsheet needs to be added to the CSS classes, which previously worked fine with Legacy Sheet
    • ex. .charsheet span{ width: 150px;}, instead of span{ width: 150px;}
  • Asterisks disappearing from CSS comments. examples & discussion(Forum)
    • Chris D. may have uncovered strange behavior with CSS comments using multiple asterisk characters. eg /******/
    • Scott C. notes that this may be an older bug and suggests to use # instead. eg /*######*/
  • detail & summary element styling is inconsistent between browsers/versions details(Forum)
  • fixed issues with @import Release Note for April 27, 2021(Forum)
    • if a @import exists, it seems it might result in roll20 ignoring the first instance of the next css class in the file, workaround is to add an empty, "sacrificial" version of the class first that will be eaten up, and the one after will work normally

LCS

Bugs that only affect Legacy Sheets.

Sheetworkers

Bugs in how sheetworkers function.

JavaScript Restrictions

Github

Bug affecting how sheets uploaded to the sheet repo work or function.

  • replacing sheet images on github doesn't always update on sheet to make sure images change on sheet when updating/replacing them, change their name/reference in the code, eg. logo.jpg to logo2.jpg.

See Also