Using accesskey with href triggers "unauthenticated sources" warning
Reported by
thomasmo...@gmail.com,
Jul 19 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: 1. Add an acceskey attribute to any link (<a href=""></a>) 2. Try to trigger the acceskey Example page with description: https://stackoverflow.com/questions/44411638/using-accesskey-in-chrome-triggers-an-unauthenticated-sources-warning What is the expected behavior? To open the linked page What went wrong? It triggers a warning that normal users won't accept because they don't see the warning. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 59.0.3071.115 Channel: stable OS Version: 10.0 Flash Version:
,
Jul 24 2017
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 24 2017
,
Jul 26 2017
,
Jul 27 2017
Able to reproduce the issue on the latest canary(62.0.3168.0) of Windows-10, Mac OS 10.12.5 and Linux Ubuntu 14.04. This is non-regressed behavior and is seen on older chrome version: 45.0.2454.101 as well. Marking this Untriaged for more inputs.
,
Aug 1 2017
This doesn't look like an `accesskey` problem, it looks like `https://www.w3schools.com/html` redirects to `http://www.w3schools.com/html/` (HTTP, not HTTPS, with a trailing `/`), which is blocked as mixed content. Replacing `https://www.w3schools.com/html` with `https://example.com` (which does not redirect insecurely) does not produce the same error.
,
Aug 1 2017
Yes that seems correct. I'm sorry for wasting your time for this. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by sandeepkumars@chromium.org
, Jul 24 2017