Mario, Yes I was erroneously using the 4.1 version while testing 5.1 (my Bad)
Every widget that is used "self closing" like <$count /> there should be > _no_ problem. They should all work. _And with the _srcName you have *one > parameter*, that can be defined in the "user line".. > > However, without customisations Count: `<$count filter="[prefix[$:/state]]"/>` works Count: `<$count filter="[prefix[$:/state]]"</$count>` does not So I think this observation still stands. Since customise will generate </$count> It will not work I do not know how to identify others without exhaustive testing or reading (understanding) widget definition code. As written with the _srcName parameter, there should be almost no limit in > using any widget. ... except may be the <$button widget, if you want more > than 1 parameter from the line. - *Can I ask?,* I have not test yet but is their any reason this would be limited to widgets?, because html could also make use of the content being applied to an attribute? - Perhaps too much to ask if there were a way to pass SOME content into the src and other as usual treated as content. - In a dreamy state you could imagine any key=value pair in the "content" being translated to attribute=value with every thing else placed in the body. Here is another experiment that has WORKED! \customize tick=style _element="style" ´style .mystyle { border: 1px solid green; border-style: dotted; } ;.mystyle Content ;Perhaps also; ´style {{myStyleSheet}} so one could have a Anyway, Best start my day Tony -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikidev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/7f02d37e-0b38-431b-8919-c6dceb65bcc6o%40googlegroups.com.