any help with an issue (char sheet)

what it should look like! this is shown in preview. this is what i get in game! the checkbox selection is missing! theres the part of the code  relaiting to the screen shots..    any reason why this is happening? (have had it working befor without issue..then it stoped!) <h3>DEFENCE:</h3> <b>HEAD DICE: </b><span name="attr_h_dice"></span><br> <b>HEAD ABILITY: </b><span name="attr_h_ability"></span><br> <b>TORSO DICE: </b><span name="attr_t_dice"></span><br> <b>TORSO ABILITY: </b><span name="attr_t_ability"></span><br> <b>FEET DICE: </b><span name="attr_f_dice"></span><br> <b>FEET ABILITY: </b><span name="attr_f_ability"></span><br> <b>ITEM DICE: </b><span name="attr_i_dice"></span><br> <b>ITEM ABILITY: </b><span name="attr_i_ability"></span><br> <h3>Consumables:</h3> <b>ABILITY: </b><span name="attr_c_ability"> <h3>CLASS</h3> <input type="checkbox" class="sheet-BARD" /><span style="background: #B97621; color: white"> BARD </span> <input type="checkbox" class="sheet-BESERKER" /><span style="background: #B9222D; color: white"> BESERKER </span> <input type="checkbox" class="sheet-DRUID" /><span style="background: #F4C385"> DRUID </span> <input type="checkbox" class="sheet-MONK" /><span style="background: #170D7E; color: white"> MONK </span> <input type="checkbox" class="sheet-NECROMANCER" /><span style="background: #817DA9; color: white"> NECROMANCER </span> <input type="checkbox" class="sheet-PALADIN" /><span style="background: #E59A70; color: white"> PALADIN </span><br> <input type="checkbox" class="sheet-RANGER" /><span style="background: #059208; color: white"> RANGER </span> <input type="checkbox" class="sheet-ROGUE" /><span style="background: #450340; color: white"> ROGUE </span> <input type="checkbox" class="sheet-SHAMAN" /><span style="background: #65EB7F"> SHAMAN </span> <input type="checkbox" class="sheet-TINKERER" /><span style="background: #4E3926; color: white"> TINKERER </span> <input type="checkbox" class="sheet-WIZARD" /><span style="background: #D32900; color: white"> WIZARD </span> <div class="bard">

So, first thing; NEVER  trust the previewer. It uses a very outdated version of the character sheet renderer that doesn't support anything that was added to character sheets in the last 7ish years (maybe more). I don't see any reason that your checkbox section of code would be missing. However, this code is probably contained in some sort of container? what does the containing code look like? And what does the CSS for that container and the checkboxes look like? And, some troubleshooting advice; in game, I'd recommend opening the developer inspector and seeing what the live html looks like. It's possible those checkboxes are there, but positioned so that they are not visible or some other css property to make them not visible. Additionally, I would highly recommend using the custom sheet sandbox to develop your sheet instead of the custom sheet game mode. The sandbox makes it much easier to load code from your computer (even easier with my autocode uploader chrome extension). And then, one bit of code advice; I'd recommend using full words in your attribute names (e.g. attr_head_dice instead of attr_h_dice ).

THANKS ..  i know preview is techy is showing what the sheet will look like..  but i used it to show the image of the missing data  .. will have to 'play' in the sandbox.. 

I'm wondering if you need to chek the legacy sanitisation checkbox. The preview is probably designed for older code. As Scott says, it should never be trusted anyway.

sorted this issue ....   just encased the section in a <table></table> the checkboxs are now visable ! <table> <h3>DEFENCE:</h3> <b>HEAD DICE: </b><span name="attr_h_dice"></span><br> <b>HEAD ABILITY: </b><span name="attr_h_ability"></span><br> <b>TORSO DICE: </b><span name="attr_t_dice"></span><br> <b>TORSO ABILITY: </b><span name="attr_t_ability"></span><br> <b>FEET DICE: </b><span name="attr_f_dice"></span><br> <b>FEET ABILITY: </b><span name="attr_f_ability"></span><br> <b>ITEM DICE: </b><span name="attr_i_dice"></span><br> <b>ITEM ABILITY: </b><span name="attr_i_ability"></span><br> <h3>Consumables:</h3> <b>ABILITY: </b><span name="attr_c_ability"> </table>

Uh oh, Rick said the "T" word ;-P backstory: most of the roll20 sheets(as well as many webpages) were first created using nothing but tables for layout.  That said, roll20 and the cyber world in general have moved on from tables(unless you specifically need to post tabular data) to using flexbox and css-grid with section, div, span, etc.  Roll20 now requires new sheets to be written without tables since there are "issues" that can arise when using tables.  I'm not sure what those specific issues are, but... Anyhow, just rambling on.  Glad you got it figured out.

I'd also point out that since you aren't actually using any feature of a table there, a div would do just as well. And if they aren't showing up in a div, you have something else hinky going on that you are going to want to track down before it becomes a bigger problem somewhere else.

thanks for the assistance guys... the sheet i created for Massive Darkness 2 .. is working fine... untill the expansion is releasd.. next project .. Homeworld  (based on the 2d20 Dune Adv in the Imperium)  if i can find a copy of the htlm / css, not on (the first 1000 files) github 

vÍnce said: Roll20 now requires new sheets to be written without tables since there are "issues" that can arise when using tables.  I'm not sure what those specific issues are, but... It's not that there are issues, exactly. Tables were never intended as a layout tool, but people used them that way because it was easier than the alternatives back before flex and grid were created. There might be issues with tables when using accessibility tools (things like screen readers for the blind) and this is something Roll20 cares a lot about. But the main thing, I think, is that using tables for layout is just bad code, and banning them is a way to enforce better standards. Itdoesn't take much effort on roll20's side, so it's an easy requirement to enforce. There's a lot of ways sheets could be improved and brought into more compliant standards, but that would take a lot of analysis work, so its understandable they only really do this one thing, because its a huge thing and can make a lot of difference.