Finally!
Great way to easily debugging and playing with JavaScript external
libraries in TW5, instead of wrapping them each time into plugin
On Thursday, 29 January 2015 23:12:01 UTC+3, Tobias Beer wrote:
>
> While having no plans of using this (yet),
> however, seeing how that cat is out of
Hi Jeremy,
It's interesting that you choose to restrict javascript usage to make it
more safe to share content. Thanks for the explanation.
Best,
Matt
On Sunday, March 5, 2017 at 3:25:01 PM UTC-5, Jeremy Ruston wrote:
>
> Hi Matt
>
> Just to add to the answers from others,
>
> I'm also
Hi Matt
Just to add to the answers from others,
> I'm also somewhat confused about why we have javascript macros then, and what
> the difference is there.
The objective of TiddlyWiki’s security restrictions is to make it possible to
safely share content between users. That requires that
Oh. nice solution. Will try this one too.
Thanks!
On Thursday, 29 January 2015 13:38:51 UTC-5, BJ wrote:
you are looking for
exports.htmlUnsafeElements = script.split(,);
but I think it would be better to include a couple of macros to switch
scripting on and off:
create a tiddler (any
Thanks Will try this today
On Thursday, 29 January 2015 15:12:01 UTC-5, Tobias Beer wrote:
While having no plans of using this (yet),
however, seeing how that cat is out of the box anyhow,
here's a single *script* macro to toggle script tags on and off, BJ
style:
That would be great. Thanks
On Wednesday, 28 January 2015 11:25:39 UTC-5, Jeremy Ruston wrote:
TiddlyWiki is designed to block JavaScript in wiki text content to make
sure that it is safe to share wiki text content. It's necessary so that we
can explore multi-user server configurations and
Sorry but I'm not sure to understand what you mean. Is it that there's a
parameter named script that will help me do what I want? Because in the
config.js, there's no script configuration to be found.
On Wednesday, 28 January 2015 19:12:02 UTC-5, Tobias Beer wrote:
It's not hard to find. If
you are looking for
exports.htmlUnsafeElements = script.split(,);
but I think it would be better to include a couple of macros to switch
scripting on and off:
create a tiddler (any name will do) and set the type to application/json
add field module-type with value macro
and insert in it
Hi BJ,
did you test this or is it a hypothetical?
Best wishes, Tobias.
--
You received this message because you are subscribed to the Google Groups
TiddlyWiki group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tiddlywiki+unsubscr...@googlegroups.com.
To
While having no plans of using this (yet),
however, seeing how that cat is out of the box anyhow,
here's a single *script* macro to toggle script tags on and off, BJ style:
http://fiddle.tiddlyspot.com
Best wishes, Tobias.
--
You received this message because you are subscribed to the Google
Hi Tobi
On Wed, Jan 28, 2015 at 2:00 AM, Tobias Beer beertob...@gmail.com wrote:
I never actually looked at the core to find what disables script tags. I'd
be curious to figure out how to enable them. Anyone wanting to mess with
your data would do the same thing. I prefer to know myself how
Am Mittwoch, 28. Januar 2015 12:49:27 UTC+1 schrieb Jeremy Ruston:
Note that script tags are allowed in text/html tiddlers because they are
safely sandboxed in an iframe.
I'm not sure, whether or not I understand sandboxed correctly.
Please go to tiddlywiki.com
Set a username
Create a
Hi Stephan
Good catch. It seems to depend on the browser: Firefox seems to allow the
cross domain access, but Safari and Chrome do not allow it in my tests.
I'll investigate whether adding the sandbox attribute improves things.
Best wishes
Jeremy.
On Wed, Jan 28, 2015 at 1:32 PM, Stephan
It's not hard to find. If you search the source tree for script
(including quotes) you'll see this in *config.js*...
Thanks for the pointers.
--
You received this message because you are subscribed to the Google Groups
TiddlyWiki group.
To unsubscribe from this group and stop receiving
TiddlyWiki is designed to block JavaScript in wiki text content to make
sure that it is safe to share wiki text content. It's necessary so that we
can explore multi-user server configurations and federation. If the act of
viewing content authored by someone else causes executable JS code to run
It make sens. Thanks!
On Wednesday, 28 January 2015 11:25:39 UTC-5, Jeremy Ruston wrote:
TiddlyWiki is designed to block JavaScript in wiki text content to make
sure that it is safe to share wiki text content. It's necessary so that we
can explore multi-user server configurations and
16 matches
Mail list logo
