Alan, Happy to follow your lead on this. Some thoughts you may not have considered?
- If the text that is used to search and or autocomplete is in a state tiddler or field, more than one widget can access it at a time. What if we simply place a search result popup along side your existing auto complete example. That is the designer crafts the desired result from a suitable combination of widgets existing or tweaked to support this? - There are always benefits to be had from maintaining modularity because as yet unconsidered combinations become available and prove to be useful. - The current $select widget is a widget even although it may leverage the html select so it seems to me to extend it to accommodate autocomplete may be the most profitable. Especially if the use of the edit-text widget within it is not extended. As I suggested previously you can for example use the edit-text input/tag options to only accept numbers in the edit field, this has value that may be lost it edit text if modified? Regards Tony On Friday, September 20, 2019 at 8:35:28 AM UTC+10, Alan Aldrich wrote: > > I agree coda, I think enhancing the popup mechanism is the way to go. I am > no longer recommending we add functionality for <datalist> for many > reasons. Even if the id issue didn't exist it still wouldn't work for the > search field. Should we start a new topic with a clearer agenda? > > > On Thursday, September 19, 2019 at 4:53:05 PM UTC-5, coda coder wrote: >> >> >> >> On Thursday, September 19, 2019 at 3:44:02 PM UTC-5, Alan Aldrich wrote: >>> >>> >>> Hopefully I am explaining this clearly. >>> >> >> Well, I'm following it ;) >> >> >>> What this means to me is we will likely need a customized solution. >>> >> >> I think so. In js, you could rebuild the datalist "live" as the input >> changes, but that's still not how you envisage it working. I really don't >> think datalist is the way to go (the id problem, as I said, is a >> non-starter, I believe). >> >> Perhaps the popup mechanism can be enhanced to support correct >> tabbing/keyboard behavior? Although, I do imagine with some heavyweight >> TWs, that might prove slow. >> > -- 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/c3aea52b-8c53-43d0-ba07-92f745b18c9f%40googlegroups.com.
