AaronX Posted October 20, 2016 Report Share Posted October 20, 2016 Hi, I hope someone from the Maxthon team can help me: how does Passkeeper/old Magic Fill target which form fields to auto-fill? And specifically, how can I stop it? A website I run has a user account system, for which Passkeeper stores and applies my own account information perfectly across log-in screens. However, it then also incorrectly applies my e-mail and password to an admin control panel for editing other user accounts. I've tried renaming the field name and id values, and only with BOTH changed has it stopped applying my e-mail address; I had to remove the password type too from the password field to stop that. autocomplete="off" is ignored on both the form as a whole and individual fields. Link to comment Share on other sites More sharing options...
7twenty Posted October 20, 2016 Report Share Posted October 20, 2016 It uses the field names as you have noted above. You can disable it from options. Or change it to manual mode, in which you'll need to doubleclick a field and choose an option from the dropdown to fill the data. Not as magic as it always autofilling, but still simple and easy enough to make it handy. Link to comment Share on other sites More sharing options...
AaronX Posted October 21, 2016 Author Report Share Posted October 21, 2016 15 hours ago, 7twenty said: It uses the field names as you have noted above. It does seem to do more than that, though. For example, at one point I had changed both name and id of the e-mail field, but still had the password as was - and it then started filling in my e-mail address in the surname field! I can only guess because surname was the last text input field before the password field so it latched onto that DOM positioning? (Despite the e-mail field being of email type, not text.) Basically, I'd just quite like it if it would obey autocomplete="off" Link to comment Share on other sites More sharing options...
7twenty Posted October 23, 2016 Report Share Posted October 23, 2016 On 21/10/2016 at 10:44 PM, AaronX said: It does seem to do more than that, though. Interesting. I was trying to play around with it in a test form on a local file. But I can't get magicfill to work on any of the fields for some reason. On 21/10/2016 at 10:44 PM, AaronX said: Basically, I'd just quite like it if it would obey autocomplete="off" I have to say the fact that it doesn't obey that is a good thing... so many extra fields to fill in manually otherwise! That said, MX should really adhere to the standard. Link to comment Share on other sites More sharing options...
AaronX Posted October 23, 2016 Author Report Share Posted October 23, 2016 8 minutes ago, 7twenty said: I have to say the fact that it doesn't obey that is a good thing... so many extra fields to fill in manually otherwise! That said, MX should really adhere to the standard. Yes. I was in two minds about it for that reason, but ultimately standards should be adhered to. I think it could at least not auto fill them in, but still offer them to be filled when the form/field gains focus. Link to comment Share on other sites More sharing options...
7twenty Posted October 23, 2016 Report Share Posted October 23, 2016 2 minutes ago, AaronX said: I think it could at least not auto fill them in, That's what manual mode is for. Doubleclick the field and choose the required dataset to fill. Link to comment Share on other sites More sharing options...
AaronX Posted October 23, 2016 Author Report Share Posted October 23, 2016 Just now, 7twenty said: That's what manual mode is for. Doubleclick the field and choose the required dataset to fill. Yeah, but I mean specifically when autocomplete="off" is set. Link to comment Share on other sites More sharing options...
7twenty Posted October 23, 2016 Report Share Posted October 23, 2016 Ahhh, ok gotcha. That would make more sense Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.