New issue
Advanced search Search tips

Issue 639338 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 639046
Owner: ----
Closed: Aug 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

websites are suddenly not navigable...seems like <a> tags malfunction or are disabled

Reported by m...@deemok.com, Aug 19 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2832.2 Safari/537.36

Steps to reproduce the problem:
1. go to this website https://chromiumbugs.appspot.com
2. follow steps 1,2 3 (meanwhile go to other websites in another tab)
3. after a while buttons like back and submit don't work

What is the expected behavior?
Buttons and clickable items (<a> tags) to do what they intend to do.

What went wrong?
Started experiencing this around 930 AM EST 08-19-16

Did this work before? Yes always.

Chrome version: 54.0.2832.2  Channel: canary
OS Version: OS X 10.10.5
Flash Version: Shockwave Flash 23.0 r0

This is obviously a very fuindamental issue.
 

Comment 1 by m...@deemok.com, Aug 19 2016

UPDATE:  While this was happening all morning long for this website and our own, I am no longer able to duplicate it at the moment.  I will update again, if anything changes.

Comment 2 by m...@deemok.com, Aug 19 2016

UPDATE:  The issue has returned.

Comment 3 by m...@deemok.com, Aug 19 2016

UPDATE:  

- reload does not fix this.  All contents in TAB are unclickable
- in same (nonworking) TAB if type new url, the new site works.  Back arrow and the original (nonworking) site works again but for a little while.
- A new TAB behaves normally for a little while until the problem comes back again

Comment 4 Deleted

Duplicate of https://bugs.chromium.org/p/chromium/issues/detail?id=639046, which has a fix up for review.

Comment 6 by meh...@chromium.org, Aug 19 2016

Mergedinto: 639046
Status: Duplicate (was: Unconfirmed)

Comment 7 by m...@deemok.com, Aug 21 2016

I see this has been fixed in Version 54.0.2835.0 canary (64-bit).

Many thanks!

Sign in to add a comment