The usual way to avoid that would be to attach the "data" prefix, say "data-myparam", right?
I like your macro trick. However, it adds a second step to the workflow. The idea was to make multiple varying widget calls with same parameters easy. With macros we will have to define each widget separately before using it. Anyway, sans such a solution, this would have to do I guess. On 12-Oct-2017 9:27 PM, "PMario" <[email protected]> wrote: > On Thursday, October 12, 2017 at 10:41:37 AM UTC+2, Riz wrote: >> >> Moreover, macros are not taking care of the second part, which is support >> for unknown parameters. >> >> For eg: I type >> >> <$button tabindex=0>My Button</$button> >> >> and the generated html fails to show the tabindex property. Tabindex is >> not yet supported as a property of button widget. Currently if we want to >> add it, we need to modify button.js. I was hoping the widgets like button, >> edit-text etc will map all unknown parameters to the generated html >> counterpart without modification. In the above example, it would generate >> <button tabindex="0">My Button<button> >> >> > You are right, that's a new behaviour, which could be implemented for > every widget, that creates DOM elements. ... > > The only problem would be to avoid parameter names, that will be > implemented into future HTML specs, which are unknown at the moment of this > writing. > > -m > > ... -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAO0b0pFx7LcpWP4fQySr381Yi8TC_gUd8xnRcccRyWJtya6E8Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
