Is there any reason that a perspective binding would behave differently in the browser than it does in the designer preview mode?
For some reason, my bindings look good in the designer, but when I go to see how they look in the browser, they are all errored saying they received null data etc.
Here is the preview
Here is the browser
Your bindings in the Designer have a value in the Designer, but that value is transient/ephemeral. When your Session begins, it attempts to obtain a value (or references a value) which is either null or references a property which doesn't exist. This can be common when scripts create properties on the fly. Make sure any references your Thermometer has within the binding for mercuryColor are present at all times, and have default values which make sense (are non-null, especially if doing any transforms which would expect string or numeric types). Finally, you may want to right-click the properties in question and select the Persistent option. This will result in the current value in the Designer being the "starting" value in use by the component until the binding resolves.
I'm having a similar issue where my views look differently in the browser vs Designer preview.
The newly added sparklines show up in Designer, but when I launch the browser either from within Designer or direct, the initial view does not show the sparklines. If I refresh the page or resize, then they show up.
Running Sessions don't always pick up all chnages on save. Data/values are almost always picked, but changes to the structure of the resource are often missed - or new resources. CSS changes are a good example of this: changes saved to the stylesheet.css resource aren't picked up in running sessions because that resource has already been loaded to the browser. Running sessions require a refresh, while new sessions will pull down the latest version of that resource.
I understand your Sparklines aren't the stylesheet.css resource, but they do change the structure of the page currently in use. We can't force the session to take saved changes, because it would overwrite things like session properties.
