Ability to disable the ability of websites to stop user pasting into form fields
Reported by
a.d.herr...@gmail.com,
Aug 7 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 Steps to reproduce the problem: 1. Go to many websites that prevent you pasting into 'confirm email' etc boxes 2. Attempt to paste into form field 3. Feel sad :| What is the expected behavior? Text should appear in the form field What went wrong? Many people make heavy use of pasting due to accessibility issues or because they find typing to be a error prone process. Forcing these people to manually enter text can lead both to more errors and physical pain. Did this work before? N/A Chrome version: 51.0.2704.103 Channel: stable OS Version: OS X 10.11.5 Flash Version: Shockwave Flash 22.0 r0 I opened this issue because it fits with other recent user first decisions such as changing the behaviour of autocomplete off: https://bugs.chromium.org/p/chromium/issues/detail?id=468153 Firefox has also made some changes to support this issue: https://bugzilla.mozilla.org/show_bug.cgi?id=542938
,
Aug 8 2016
I don't believe that the issue you linked to is the same. That issue is in reference to autocomplete whereas this issue is with respect to pasting.
,
Aug 15 2016
Thank you for providing more feedback. Adding requester "durga.behera@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 15 2016
In general, it is not the place of the browser to intervene with the website. If the website chooses to disallow pasting into a particular form field, the browser should respect that. If the author really wants that behavior, they can always find workarounds to whatever the browser implements. If there is a decision to change this behavior, it should be proposed as a spec and implemented by all browsers. Otherwise we will just see more fragmentation.
,
May 19 2017
When it involves the security of the user I'd argue that it is always the place of the browser to intervene on behalf of the user. Examples: - Cross origin requests - Chrome warning you if a http page has a password field - Chrome ignoring autocomplete="off" on password fields I believe the last point particularly parallels this request as it was not standard led. Some evidence that the industry is struggling to tackle this issue through best practice and requires the browser vendor to intervene: https://www.ncsc.gov.uk/blog-post/let-them-paste-passwords |
|||
►
Sign in to add a comment |
|||
Comment 1 by durga.behera@chromium.org
, Aug 8 2016Components: -UI UI>Browser>Autofill
Labels: Needs-Feedback