Alan, Ahh I understand the need for a matching "list" attribute.
I imagine then we could put a data list for values in a tiddler that is displayed silently, or perhaps in a tiddler tagged $:/tags/Macro then access it anywhere with your proposed edit-text improvement. This is great because then multiple edit-text widgets can refer to a standard datalist to populate values. The range type looks good, There is a range widget available already but it does not handle the example data you gave, a set of values not in a simple range. One thing that may be important to you and may enable another hack with the datalist elements is what is already possible with the select/options tags. See here for the select widget <https://tiddlywiki.com/#SetWidget>. Note that the options are generated using the list widget so the options can be pulled from any tiddlywiki filter thus reference, title, field or variable. It would be nice if your proposed datalist could do this as well. On another relevant aside the edit-text widget currently permits the setting of the html type and tag https://tiddlywiki.com/#EditTextWidget I raised this in a post some time ago see the image in the first post of https://groups.google.com/forum/?hl=en#!searchin/tiddlywiki/html$20edit-text|sort:date/tiddlywiki/4aCyZ3FAq9U/todMTtt-AgAJ In this post I tested all possible alternatives at the time and a number work well. Love your work. Regards Tony On Thursday, September 19, 2019 at 9:22:32 AM UTC+10, Alan Aldrich wrote: > > Tony, > you are correct. <datalist> itself doesnt render anything. It requires an > input element with a matching "list" attribute. In fact I believe datalist > element can be placed anywhere in the code, not necessarily directly under > the input element. > > I just learned something else about the datalist element you may find > interesting. In Chrome, you can use it on a "range" type input and it will > add marks to the slider. It seems browsers vary on their implementation of > the datalist element. I added a new example for this at: > http://alans-sandbox.tiddlyspot.com/ > > > > On Wednesday, September 18, 2019 at 5:41:02 PM UTC-5, TonyM wrote: >> >> Alan, >> >> *Your proposal is missing nothing! Great I support it fully.* >> >> But I was suggesting an additional more general solution. >> >> For example this "works" in vanilla tiddlywiki >> Except you can not access the result >> <select id=sresult> >> <option value="volvo">Volvo</option> >> <option value="saab">Saab</option> >> <option value="mercedes">Mercedes</option> >> <option value="audi">Audi</option> >> </select> >> As a result we need to use the $select widget. >> >> Interestingly >> <datalist id="testlist"> >> <option value="Chrome"></option> >> <option value="Firefox">Default</option> >> <option value="Safari"></option> >> <option value="Opera"></option> >> <option value="Internet Explorer"></option> >> <option value="Microsoft Edge"></option> >> </datalist> >> is not even visible in tiddlywiki, unlike select/option tag. >> >> However If we could access the result you would not even have to revert >> to a widget. But we should still adopt your solution. >> >> Regards >> Tony >> >> On Thursday, September 19, 2019 at 8:18:57 AM UTC+10, Alan Aldrich wrote: >>> >>> Tony, >>> >>> "...because we can't reference the result. This datalist method is a >>> perfect example. You can code the html and it works except you can't access >>> the result" >>> >>> Am I missing something? the example in the demo works. The result is >>> stored in a Tiddler called TestData. >>> >>> >>> On Wednesday, September 18, 2019 at 4:35:20 PM UTC-5, TonyM wrote: >>>> >>>> Alan >>>> >>>> I support this request whole heartedly because it is a despratly needed >>>> missing feature. >>>> >>>> I see the value in the edit text widget but also suggest also improving >>>> the existing select widget or even a new widget. >>>> >>>> ------------ >>>> >>>> However I would like to add I see a number of gaps like this between >>>> what we can do in tiddlywiki and what is available in html5. We could let >>>> this evolve and address these gaps as they are raised like this one. >>>> However I think there would be value Actualy hunting for these differences >>>> and accommodating them in tiddlywiki. >>>> >>>> The fact is a lot of html5 features are denighed from us because we >>>> can't reference the result. This datalist method is a perfect example. You >>>> can code the html and it works except you can't access the result. This is >>>> to do with how html references the dom but not the one tiddlywiki core >>>> uses. >>>> >>>> I believe strongly that a creative guru with tiddlywiki and dom skills >>>> could however find a way to let tiddlywiki access the result of a html >>>> operation and make it available, if only to the local wiki text. This >>>> would >>>> open many html5 features up for use in wiki text including your current >>>> datalist example. Not withstanding this I think your suggestions or >>>> versions there of, should be implemented. >>>> >>>> Regards >>>> 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/8d2f945b-0345-46b0-b928-f597f1e05d05%40googlegroups.com.
