@JackWellborn Thanks for all the input! A few quick notes before I head to bed… ![]()
-
I’ll look into it but not right away. I want to get the basics right first.
-
I’ve had some issues running JS in background tabs in the past due to browser-internal throttling / energy conservation, so for now it’s “active tab” only. I’ll check again, but see (1).
-
I agree but I also believe in the “do one thing right” approach, especially when Sindre Sorhus’ Actions is available, is free and brings good list management actions. So, I’m a bit on the fence…

-
In my dev build I’ve added looking up fields by
idattribute in addition to the existingnameattribute and CSS selector. I’ve already implemented new form-related actions and parameters, and I’m pretty happy with what I have so far. I’ll push the new TF build out tomorrow, I think. I’ve started documenting all actions today but I didn’t get around to writing up the “Web Pages” section which contains the forms stuff. -
Interesting approach, I’ll take a peek! The file threw me off due to the extension, until I realized I looked at JXA, not AS.
My code treats form fields differently depending on their type. Yes, the Element.valueis set but you’ll have the option to fire achangeevent, too. Seems to work but I’ll need to check for the undo history issues you’ve mentioned.