I have been aware of issues with 1P filling in the wrong fields on some sites for a long time, but I had not bothered to report anything because I was always trying to get something actually done, and manually copying and pasting info took care of the problem for that moment. Until today, I wasn't aware of the "Report Website Issue" feature, but now I will definitely start using it to report specific issues.
My question is more general. The most common situation I've seen 1P fill in the wrong fields for (not the only case by a long shot, just the most common recurring issue) is when a site's login page contains username/password fields for both logging in and creating a new account. 1P always seems to choose the new account fields rather than the login fields. This behavior is consistent across multiple websites.
A prominent site this can be tested on is https://linkedin.com/. If you log out from LinkedIn then visit their homepage (not the "Sign In" link given when you log out), you will see that in the center of the page there is a box for creating a new account which includes email and password fields, but there is also a pair of regular sign in fields at the top of the page. (And yes, I'm going to report the specific site after I finish this post. I'm using it as an example here.) This is typical of the kind of pages I'm talking about.
So my question is: might there be a way to fix this particular issue within 1P in general, rather than reporting each website individually? For example, if 1P finds more than one field on a page labeled "password", it might ask the user which one to fill the first time, and then store that for the future? The page code should contain something that distinguishes those fields internally.
Similarly, when 1P saves a new login entry from a site's "new account" page, this tends to mess up the autofill fields as well. In these cases, 1P stores the account creation page as the go-to page for the site (which IMO should never happen, since you're not likely to need to go back to that particular page again), and while it recognizes the domain and offers the correct login info, it frequently can't match the fields because the fields on the account creation page and those on the sign in page often aren't labeled or identified the same. When I find one of these cases, I have to go into the saved login and edit the stored URL, and then I usually have to do the manually copy-and-paste thing again.
As with the other issue, might there be a way for 1P to recognize that it's pulling info from an account creation page, and modify its behavior accordingly? I'm not sure what might be the best default behavior.