Hi James,
Maybe putting a parameter after the URL for the reload would make the
widget think it's worthy of a complete reload.
like so:
https://my.big.site.com?12345
Haven't tried it, just thought of it.
Phil Davis
On 11/3/18 9:55 PM, James Hale via use-livecode wrote:
Further exploring from my previous post.
Making a standalone of the stack.
Simply reloading the html page still does not use the modified css (as was the
case in the IDE)
But, deleting the browser widget and recreating it before loading the page and
the modified css is recognised.
So the deletion/creation will work but can only be seen in a standalone which
is a pain, but not a deal breaker.
Still, it would be nice to know what's going on.
James
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
--
Phil Davis
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
