hi All, i think this question has been asked/answered before, but has anyone experienced the situation where when the options of a select have been changed in a loop-tpl and then the selected attribute doesn't respond?

what do you mean by “doesn’t respond”?

meaning that when the options change, even though the selected attribute is being set correctly (I can inspect it), the correct option is not actually selected on the web page

is it a plain <select> or some javascript plugin?

plain old select

this seems to work:

(page "index.html")

(defc items [1 2 3 4 5])
(defc selected 1)

(defn- remove-last [_]
  (when (seq @items)
    (swap! items pop)))

(defn- append [_]
  (swap! items
    (fn [items]
      (if-let [l (last items)]
        (conj items (inc l))
        [1]))))

(html
  (body
    (div
      (h1 "Select")
      (select
        (for-tpl [item items]
          (option :id (cell= (str item))
                  :value (cell= (str item))
                  :selected (cell= (= item selected))
                  :change (fn [_] (reset! selected item))
                  (text item))))
      (button :click remove-last "Remove last")
      (button :click append "Append"))))

now you are setting selected somehow, right?

i am

updated the snippet

does this look like what you’re trying to do?

yes, I think from looking at this i may have a handle on the problem

was doing some hoplon with @candera today and he showed me some stuff he was doing with document fragments

realized: what if document fragment is what loop-tpl should return?

altho i don't know if a document fragment "disappears" if you append one to an elment

like if you make a doc fragn w/ 3 li kids, and then append the frag to an ol. do the kids become children of the ol?

all questions i could answer for myself in 30 seconds of js console, brb

ok wow. when you appendChild a document fragment to an element, the fragment disappears. its children are spliced in to the new parent

the frag object is still around, but its children are emptied