Issue 914451: Autofill does not respect autocomplete="off" (bugs.chromium.org)

Article summary

The article discusses an issue with Chrome's autofill feature not respecting the autocomplete='off' attribute, but the article text itself is not available. Commenters discuss the implications of this issue and the broader topic of browser dominance and standards compliance. Chrome's behavior is seen as potentially frustrating for users and developers alike. The issue is related to security and user experience considerations.

Main themes

• browser dominance
• standards compliance
• autofill and security
• user experience
• browser development

What commenters say

• Chrome's disregard for autocomplete='off' is a problem for developers and users who value security and control over form data.
• The browser's behavior may lead to unintended disclosure of personal information and is therefore irresponsible.
• Some commenters argue that autocomplete='off' is used for security theatre and that password managers should be able to handle it.
• Others believe that Chrome's actions are a manifestation of its dominant position in the browser market and a threat to the open web.
• The use of autocomplete='off' can prevent password managers from working correctly, causing frustration for users who rely on them.
• Chrome's decision to ignore autocomplete='off' may be motivated by a desire to improve user experience, but it raises concerns about security and privacy.
• The issue highlights the tension between browser vendors and developers, with some arguing that browsers should respect HTML standards and others believing that they should take a more active role in shaping the user experience.