Yet another use case that demands a different default comment mechanism, as the previously discussed {#...#} construct (or something similar). With it, these conditional comments wouldn't be an issue.
-Asbjørn
--
You received this message because you are subscribed to the Google Groups "Spark View Engine Dev" group.
To post to this group, send email to spar...@googlegroups.com.
To unsubscribe from this group, send email to spark-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/spark-dev?hl=en.
Yep, it will expand leading ~’s in the html attributes that are known to be uri values.
Thanks. :)
There’s another feature hidden in ~ that you can find buried in the docs for the config settings.
http://sparkviewengine.com/documentation/configuring#Sparksettingsinconfigfile
In the spark/pages/resources section you can change your production config to replace various ~/xxx prefixes with some alternate value. Putting content on cdn, for example. Works with ISparkSettings in code also.