Re: htmx progress indicator problem - might be caching

2023-12-02 Thread Mike Dewhirst
On 2/12/2023 5:42 pm, Mike Dewhirst wrote: I'm now thinking/wondering if a htmx timed execution - say every one or two seconds - might call a view which monitors a singleton being updated by the main view kicked off by the form's submit button. Well that almost worked! I can update the singlet

Re: htmx progress indicator problem - might be caching

2023-12-01 Thread Mike Dewhirst
On 2/12/2023 12:19 am, Thomas Couch wrote: Can I just check I understand the broader requirements here: * The user completes the form, which includes a list of items, and clicks submit * For each item in the list you want Django to create a new object and save it to the database * It tends to

Re: htmx progress indicator problem - might be caching

2023-12-01 Thread Thomas Couch
Can I just check I understand the broader requirements here: * The user completes the form, which includes a list of items, and clicks submit * For each item in the list you want Django to create a new object and save it to the database * It tends to be a very long list and/or each item takes a

Re: htmx progress indicator problem - might be caching

2023-11-29 Thread Mike Dewhirst
On 29/11/2023 9:56 pm, Thomas Couch wrote: Not sure if it's related, but you've got a div inside a p element there: That'll probably get corrected by the browser to: It all seems OK to my untrained eye and things stop working if I play with those elements. I'll take them out later and re

Re: htmx progress indicator problem - might be caching

2023-11-29 Thread ELVIS MAKASI
Greas Le mer. 29 nov. 2023, 11:57, Thomas Couch a écrit : > Not sure if it's related, but you've got a div inside a p element there: > > > That'll probably get corrected by the browser to: > > > > Another thing is, it doesn't look like there's anything linking the submit > button click to t

Re: htmx progress indicator problem - might be caching

2023-11-29 Thread Thomas Couch
Not sure if it's related, but you've got a div inside a p element there: That'll probably get corrected by the browser to: Another thing is, it doesn't look like there's anything linking the submit button click to the initial htmx request, and there's no htmx in the response. Have you trie