Question thread #62

[pauamma]

It's time for another question thread!

The rules:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.

Comments

[pauamma]

Is there a tutorial of how to fill these fields programmatically?

If there is, I'm not aware of it. But I think it would be interesting to have one, if you feel like writing it as you go along. Alternatively, this may be a job better suited to the new API we have in development, if that is usable from GM scripts. (Which it may not be. I know very little about GM. Also, there might be no API to prepopulate that form without posting, if that's what you want to do.)

[bytebuster]

Thank you for the answer, this is what I was afraid of. :)

Yes, my goal is to pre-populate the form so that it remains to only press the "Post" button. I tried to direct populate the fields that are submitted along with the form, but:

1. this would not display on screen
2. if you simply press "Post" button, some fields (Tags and something else, don't remember for sure) is not posted to the server upon the form submission.

[bytebuster]

Wow, that was easy. Dispatching a 'change' event works for all three JS-rich elements: To-Community dropdown (after setting its .selected), Icon dropdown, and Tags string input (after setting its .value).
Here's how to do it for Tags:

const CLS_INPUT_TAGS = "autocomplete-input";
elTags = document.getElementsByClassName(CLS_INPUT_TAGS)[0];
elTags.value = "tag1, tag2";
elTags.dispatchEvent(new Event('change'));