Replying to tweets and going back to the Twitter timeline page forces Chrome to go back a page or two
Reported by
kevinjwe...@gmail.com,
Oct 20
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36 Example URL: http://www.twitter.com Steps to reproduce the problem: 1. Reply to a tweet on twitter 2. Click outside the tweet box to go back to the timeline page 3. Chrome automatically goes back a page or two What is the expected behavior? Chrome should be staying on the twitter timeline page. What went wrong? Whenever I reply to tweets on Twitter and then click outside the tweet box to continuing scrolling through my timeline, it forces Chrome to go back a page or two. Does it occur on multiple sites: No Is it a problem with a plugin? N/A Did this work before? Yes Does this work in other browsers? N/A Chrome version: 70.0.3538.67 Channel: stable OS Version: OS X 10.14.0 Flash Version:
,
Oct 21
,
Oct 22
Unable to reproduce the issue on mac 10.13.3 using chrome reported version #70.0.3538.67 and latest canary #72.0.3587.0. Attached a screen cast for reference. Following are the steps followed to reproduce the issue. ------------ 1. Replied to a tweet on twitter. 2. Clicked outside the tweet box to go back to the timeline page. 3. Observed that chrome stayed on the twitter timeline page as expected. kevinjweiner@ - Could you please check the issue on latest canary #72.0.3587.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Thanks...!!
,
Oct 31
Are you able to reproduce on stable build 70.0.3538.77?
,
Oct 31
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 31
Unable to reproduce the issue on mac 10.14.0 using chrome latest stable #70.0.3538.77 as per comment #0. Observed that chrome stayed on the twitter timeline page as expected. Attached a screen cast for reference. Hence, removing the Needs-Bisect label and requesting someone from Blink team to please have a look into the issue. Thanks...!!
,
Nov 1
This sounds likely to be caused either by an extension, or just a bug in an experiment that Twitter is running. Please try using a fresh profile with no extensions installed (as suggested in #3). If possible it would also be helpful to know if the problem reproduces on a different computer, or with a different (perhaps brand new) twitter account.
,
Dec 3
Mac triage: WontFix old issue without feedback or repro steps. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by kevinjwe...@gmail.com
, Oct 207.3 MB
7.3 MB View Download