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
This post has been closed. You can still view previous posts, but you can't post any new replies.

API generated CSS properties being removed

1525116855

Edited 1525118104
Scott C.
Forum Champion
Sheet Author
API Scripter
Compendium Curator
So, not sure what has changed on Roll20, but as of today messages generated by my API scripts that have a background-color specified now show with the default or Roll20 specified background-color. These scripts worked previously, and have not been changed since. The value of the inline specified background-color property is apparently being stripped out by the API chat parser because when inspecting the chat message, there is no value specified for the background-color property. Example Code: on('ready',()=>{     sendChat('','/w gm <div style="border: 1px solid black; background-color: white; padding: 3px 3px;">Test Text</div>'); }); Actual Output: Expected Output (photoshop mockup and what used to happen): Any ideas? -Scott EDIT: Was discussing this with Aaron, and he suggested trying to use just the background property. This does appear to work, however this change probably breaks the chat based menus for most scripts that use them. on('ready',()=>{     sendChat('','/w gm <div style="border: 1px solid black; background: white; padding: 3px 3px;">Test Text</div>'); }); Output using background as opposed to background-color: EDIT 2: It looks like this is affecting more than just background-color as well. Font-family is also being stripped out. Also, looks like it is not a roll20 issue. Works fine in firefox. Aaannnd, seems to have resolved itself, sorry for the false alarm.
1525117417

Edited 1525118082
The Aaron
Pro
API Scripter
108 of my scripts are affected by this. Actually, this seems to be a weird chrome bug...