Apple should not be 'honoring the site requests not to store passwords'. That is something that should be under the user's control. This is the whole point of the keychain. I have the password to the keychain. I put my keys on it. It is supposed to then unlock things. This all used to work. If Apple wants to 'honoring the site requests not to store passwords' then they should make that a preference so that we users can turn it on and off at our need.
The result of this sort of behavior is that people will use common passwords between many sites and passwords that are insecure rather than using good quality passwords. Apple is decreasing online security with this move.
I don't know if this of any help but... I've done a few coding examples with web FORM and Safari and here's a brief summary of my observations:
So what is the impact to this? Well, if like me, you use Mac OS X Server and their Wiki, well, the username / password are not saved... in their own application... (And by the way, why is there a "Remember me" checkbox if it never works? Anybody understands what it does??).
I haven't spent too much time on this, but it someone would have "rules" on how to configure a FORM element (and its children) in order for Safari to save the information, that would probably help us understand (and help programmers make the right design choices).
Well, everyone following this thread should be happy to know that this is fixed in Safari 7! Actually, Apple has done something quite interesting: they've added an extra security layer that forces you to check a box if you want to bypass the "do not Autofill" requests from web sites.
This option is located under Preferences --> Passwords.
So, simply check this box and Safari pretty much saves every password you want.