You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using sassdown without custom template enabled, the iframe ID's generate a random ID like: iframe_abcde , but when I use the latest template.hbs It creates numerical ID's like: iframe0, iframe1, etc.. Is the former meant to prevent caching, because I do have some browser caching issues using Firefox.
The text was updated successfully, but these errors were encountered:
No, it was not to prevent caching. I simply opted for the more straightforward indexed naming later on, but the npm version has not yet been updated. Do the randomly generated IDs prevent your caching issue occurring?
When using sassdown without custom template enabled, the iframe ID's generate a random ID like: iframe_abcde , but when I use the latest template.hbs It creates numerical ID's like: iframe0, iframe1, etc.. Is the former meant to prevent caching, because I do have some browser caching issues using Firefox.
The text was updated successfully, but these errors were encountered: