![]() I’ll keep this issue in mind if I am able to continue developing the extension though. I’m making a lot of progress on scoping out the immense scale of changes that will be required in the next 6 months but have yet to reach a level of certainty that is sufficient for me to switch to working on this full time, which is what will most likely be required to meet Google’s new requirements (“MV3”). I don’t plan to make any further Kee releases until I’ve confirmed that it will be possible to release a viable version in 2023. The same login is required to manage your. To access My Account, you need to create a login. My Account lets you manage your company's purchases, subscriptions, contacts, payment and billing information, and service requests. ![]() Learn how to resolve issues you have with accessing My Account. Bumping that up to 40 for example, should resolve this specific case but until we run some detailed tests, we can’t be sure if it will also have a detrimental side-effect on other situations (making Kee pick the wrong form more often). Canada (French) Resolve issues with My Account login. All of the figures in that algorithm are semi-arbitrary and only really stay the same while it looks like everything is working well. More long-term, we could experiment with a new version of Kee that slightly increases the visibility bonus applied to fields (currently it’s 35 on line 235 of formFilling.ts). I’m not certain that will work though and it might have other undesirable side-effects but it could be worth a try. It’s counter-intuitive but if you could set an additional form field entry for one of the “new password” fields then the additional match accuracy that comes from that being found in the page might trick Kee into thinking the form is more relevant. I think that the relevance of the form is being reduced by the multiple hidden password fields and therefore the form is ignored even though one field does match. Match Text ID: ius-password,ius-sign-in-mfa-password-collection-password,ius-sign-in-mfa-password-collection-confirm-password Match Text ID: ius-identifier,ius-signin-userId-input,ius-sign-in-mfa-password-collection-current-password Match Form ID: ius-form-sign-in,ius-sign-in-mfa-password-collection-form Here is my current per-site config for Intuit. ![]() Then I also included the ID for the real password field which is ‘ius-sign-in-mfa-password-collection-current-password’ but it still doesn’t work. Today, I encountered a new one, where they marked as INACTIVE 3 of 6 accounts I maintain on. Even when you point it out to them, they are like deer in the headlights. I went and excluded them all in the per-site settings. The Mint team seems unable to fix them, so if you have a financial institution, say a minor one like Charles Schwab, Mint is unable to ingest data properly under some conditions. Looking at the HTML, it seems they have a whole bunch of hidden password fields for different workflows, like resetting passwords and such. To troubleshoot issues with your Mint account, you may need to disable your internet browsers password manager. It seems Kee is properly matching the site URL because it shows up in the list, but it’s not finding the password field as it won’t fill it out. I’m unable to figure out how to get Kee to fill out the correct password field for since they updated to mutli-step.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |