Plugin Author
Yani
(@yaniiliev)
Thanks for bringing this to our attention! That’s definitely unexpected behavior, and I understand how frustrating and risky it can be.
It seems like Yandex Browser is mistakenly identifying the DB replacement fields as login fields and autofilling them. This is likely due to the way the browser’s autofill logic works rather than an issue with the plugin itself.
I have checked the fields and there is nothing that would trigger the autocomplete in the browser.
Let me know if you see something wrong. Here is the actual code:
<div>
<input class="ai1wm-query-find-input" type="text" placeholder="Search for" name="options[replace][old_value][]">
<input class="ai1wm-query-replace-input" type="text" placeholder="Replace with" name="options[replace][new_value][]">
</div>
I’d suggest reporting it to Yandex Browser support, as it might be something they can adjust in their autofill behavior.
I’d suggest reporting it to Yandex Browser support, as it might be something they can adjust in their autofill behavior.
I reported them, and as they told, I did some tests and the problem repeated in Mozilla as well screenshot (but not in Chrome and Opera) so this is a cross-browser bug that should be fixed from your side because Yandex will not fix cross-browser problems I guess. Basically, there are many ways to make it safer, like doing a separate menu for field replacement etc, the current option looks too unsafe and vulnerable for unintentional inputs.
Plugin Author
Yani
(@yaniiliev)
Thank you for letting us know.
Could it be a browser extension that you are using? Do you see any errors in the code that I shared above?
I do not see any issues in the code of the plugin that could be causing this and I have not heard of other reports like this before. It is pointing towards a specific browser issue or extension.
I admit I have not used Yandex browser and while we try to make the plugin available for everyone, it is not something that we can perform quality assurance on and improve. I wish I had a solution for you but I am out of ideas here.
No, the bug is cross browser and happens both on Yandex Browser and Firefox with extensions disabled. The problem can be solved for sure with a separate menu that requires confirmation after input or a checkbox.