New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 726695 link

Starred by 2 users
Status: Archived
Owner:
wfh@chromium.org
Closed: Sep 24
Cc:
ajha@chromium.org
█ kavvaru@chromium.org
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:Send feedback button is not seen after the tab is killed from second time

Project Member Reported by keerthan...@techmahindra.com, May 26 2017 
Chrome Version: 60.0.3012.0
OS:Ubuntu 14.04, Windows

What steps will reproduce the problem?
(1)Launch chrome and Open any webpage(Eg: Hit F1 for help page)
(2)Type chrome://kill in omnibox and observe the Reload/Sendfeedback Button
(3)Reload the page and repeat step 2 and Follow the same steps for any other page(Eg: www.youtube.com)

Expected: Send feedback button should be seen after the tab is killed from second time.
Actual:Send feedback button is not seen after the tab is killed from second time.

NOTE:Send feedback button should be seen for the first reload of other pages. Instead, Reload button is seen.

This is a Regression Issue seen from M-60.

Manual Bisect Info:
==================
Good Build:60.0.3104.0
Bad Build: 60.0.3105.0
killActual.ogv
1.5 MB View Download
kill_Expected.ogv
1.9 MB View Download

Comment 1 by ajha@chromium.org, May 26 2017

Labels: OS-Mac
Status: Untriaged (was: Unconfirmed)
Issue is reproducible on the latest canary version: 60.0.3112.0 on Mac OS 10.12.4 as well.

Comment 2 by sandeepkumars@chromium.org, May 26 2017

Labels: -Needs-Bisect hasbisect-per-revision
Owner: brettw@chromium.org
Status: Assigned (was: Untriaged)
Using the per-revision bisect providing the bisect results,
Good Build: 60.0.3104.0 (Revision: 473014)
Bad Build: 60.0.3105.0 (Revision: 473393)

You are probably looking for a change made after 473285 (known good), but no later than 473286 (first known bad).


CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/997f15ecdcb2c945e1751199499ba86b1e34613c..462b7cae8824b4eb54e028b42da50f25ab4b0615

@brettw: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Review URL: https://codereview.chromium.org/2897573004

Thank You.

Comment 3 by sandeepkumars@chromium.org, May 26 2017

Owner: wfh@chromium.org
Correction
==========

Below is the possible suspect.

Review URL: https://codereview.chromium.org/2885143009

@wfh: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Thanks!!!

Comment 4 by robliao@chromium.org, Sep 24

Status: Archived (was: Assigned)
Archiving old bugs that have only received trivial updates for some time.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
►

Sign in to add a comment