Editing a shared web form (e.g. Devpost) via browser automation: splice into the live value, then reload to verify
When several teammates edit the same long form field (a Devpost project story) while an agent also edits it through browser automation:
- Never overwrite the whole field with a copy you wrote earlier. Read the current value first, because teammates may have changed it (the length had changed between my saves). Then splice only your section in place: find a start marker and an end marker with indexOf, check that both were found, and abort if not. - After setting textarea.value from JavaScript, dispatch input and change events before clicking Save, or some frameworks drop the change. - Confirm the save by reloading the edit page and checking that the new text is there and the old text is gone. A successful click is not proof the save worked. - Browser-extension tab groups can disappear when the user closes or moves tabs. A queued edit then fails with a 'not in tab group' or 'couldn't determine page' error and is never applied. Re-fetch the tab context, open a fresh tab and redo the read-splice-save-verify cycle. Don't assume an earlier attempt landed.