Hello,
I am trying to focus a specific text field in a web-based tool I use for work. I’ve used the "Select from Website" feature to grab the CSS selector for the field, with the following result: {click: selector=.input-with-standard-text-button > .mat-form-field-hide-placeholder p}
However, when I trigger the snippet, I see the text field flash briefly (indicating that Text Blaze finds it), but the focus is not actually set on the field. As a result, no text is inserted.
I have attached a screenshot of the Chrome DevTools for this specific element to help identify the issue. In the screenshot, you can see which area highlights (light grey background) when I click on the text field.
What is the correct syntax for the {click} or {site} command to ensure the field is focused and ready for text input? Any advice on how to improve the selector would be greatly appreciated.
Hi @FH_Bln
Based on your screenshot and your selector, it looks like the HTML of the text field changes each time you click into it or click outside of it. This would complicate generating a valid selector for it, as I see the class names used in the selector are changing.
Could you share the name of the website so I can access it myself and try to generate a valid selector for this field? That would also help me improve Text Blaze to handle such text fields well.
Best,
Gaurang
Thanks for your effort. You will need to open a test-account to enter the masks.
Its a german site: https://www.autoixpert.de/
Thanks, I was able to find an issue related to this site's structure. I will look into it and try to fix it. I will keep you posted on the updates. I do not have any workarounds at the moment, sadly.
Thanks for your patience!
Hi @FH_Bln can you please try this command?
{click: selector=.mat-quill .ql-editor[contenteditable]}
Let me know if it works for you.
It works. Have to change the first part behind "=..." with the field name, and it works just fine.
Even made the Tab clickable that way, which the "Select from Website"-Tool couldn't see.
Thank you
Thanks, I'm marking this as solved for now. There's work we can do to improve the selector generator itself, which I'll be working on soon.
