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 "BCS/Bugs"

From Roll20 Wiki

Jump to: navigation, search
m (Sheetworkers)
m (default value & translation bug)
Line 6: Line 6:
 
=Bugs=
 
=Bugs=
  
* using optgroups in select doesn't work on custom sheets, even though it works on existing sheets like [[Free Spacer]]
+
* '''using optgroups in select doesn't work on custom sheets''', even though it works on existing sheets like [[Free Spacer]]
 
** {{fpl|10017485/ discussion}} May 2021
 
** {{fpl|10017485/ discussion}} May 2021
* "Newly-dropped characters now must fully resolve before closing the window"
+
* '''"Newly-dropped characters now must fully resolve before closing the window"'''
 
** {{fpl|10066145/ rapport}} by [[Keith]] May 2021
 
** {{fpl|10066145/ rapport}} by [[Keith]] May 2021
 +
** possibly fixed
 +
* '''translation special character bug''' {{fpl|10111515 discussion}}
 +
* '''changing default value of attributes will change untouched values of existing sheet.''' Ex. <code><input value="a"></code> to <code><input value="b"></code>
 +
** {{repo|Roll20/roll20-character-sheets/pull/8955 example of instance of this bug being reverted}}
 
==CSE==
 
==CSE==
 
Bugs related to [[CSE]].
 
Bugs related to [[CSE]].

Revision as of 09:10, 26 May 2021

Main Page: Character Sheet Enhancement

Character Sheet Creation
Getting Started


Reference


Tools & Tips


Git/GitHub GitHubLogo.png


Other

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
  • "Newly-dropped characters now must fully resolve before closing the window"
  • translation special character bug
  • changing default value of attributes will change untouched values of existing sheet. Ex. <input value="a"> to <input value="b">

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
    • Workaround: since nested quotes and/or queries that include special characters may break in CSE-mode, try substituting the ampersand character as well. ie &quot; should be changed to &amp;quot;.
  • 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.
    • 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
  • fixed issues with @import
    • 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 GitHubLogo.png 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