2. Using the content of a <div contenteditable="true" />
still not an attribute, content is still not selectable even if editable
3. Using <datalist> to autocomplete <options/> on an <input/>
the killer here is really the same as above. You can autocomplete and technically sub-string 'search' terms based on the native implementation of an <inputs list="whatever"/>
the problem is after you select an option, no attribute is set in the html.
further more, you cannot style or manipulate options you've created for the dataset in the actual options list because the functionality is handled natively. I attempted setting <dataset style="position: absolute;"/> and was hoping the static list (assuming it was the same when auto-completing) would start to disappear
4. Form submit allowing autocompleted value to be submitted as the slug
we can substring search the <options />, but we can't reduce the list of options after search. Fine.
can we at least utilize the search result with a form?
it's either a query param or a POST that has a body