Comment by dccoolgai
I love this! Great work! Just an idea here, since you already have a form with the `action` set up, you could do some kind of `noscript` section with like 10 preset `input` elements, where the "n+1"th input appears when strings are present for the "nth" ones (using :has or something like that... the internet is lousy with examples of how to do this kind of thing). To go really hardcore "progenhance" you could even wrap that all in a @supports CSS rule. (So "if you don't want to use CSS, here's all 10 inputs. Have fun, sailor.")
Good idea. I get it. But I do not find it "clean" as Travis states.
Have a quick turn around time on the form. Let it be a server problem. Have a hidden field on the form set to "nojs". Let javascript set this to "js".
The server can then decide if this is a bulk edit or not. It can then decide it will batch approvals into one mail or wait a little longer.
Then you can optimize on what you find most clean and/or works best.
Have one form field for easy entry and turn around. Ten as you suggest? But what is the optimum number? 3? 20? And is it "clean" to have 20 form fields which the javascript version then will roll back into one.
So the non-javascript version will never be better. Somethings gotta give. But submitting a form can be superfast. And the page refresh will be super fast. Such is life without javascript.
And now I realize that I made an implied server optimization: Mail approval should in my mind be batched and dampened. 10 seconds might be enough.As long as new inpit is coming we can postpone approval anyway as the user is busy. Findong the correct number is the magic trick. Not too fast. Not too slow.