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

Issue 788291 link

Starred by 1 user
Status: Duplicate
Merged: issue 96041
Owner:
a...@chromium.org
Closed: Nov 2017
Cc:
█ divya.pa...@techmahindra.com
█ ramyan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Chrome dosn't update tab title if no response

Reported by khaweron...@gmail.com, Nov 24 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce the problem:
1) Open http://appsbirdy.com/chrome_bug.php
2) Above page will set page title 'Bug in Chrome'
3) Now refresh page. This time it will not show any output. But chrome still shows page title 'Bug in Chrome'.

Details
When you load page first time it will output '<title>Bug in Chrome</title>' and set cookie. When you reload page it will not output html. If you want to repeat step 1, please remove cookie set by page.

What is the expected behavior?
Chrome was supposed to change page title to 'http://appsbirdy.com/chrome_bug.php' because page didn't set title

What went wrong?
Chrome didn't update page title

Did this work before? N/A 

Chrome version: 62.0.3202.94  Channel: stable
OS Version: Windows 10
Flash Version:

Comment 1 by divya.pa...@techmahindra.com, Nov 28 2017

Cc: divya.pa...@techmahindra.com
Components: UI>Browser>NewTabPage
Labels: -Type-Bug -Pri-2 hasbisect-per-revision Triaged-ET M-63 Needs-Triage-M64 OS-Linux OS-Mac Pri-1 Type-Bug-Regression
Owner: a...@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on reported chrome version 62.0.3202.94 and latest beta 63.0.3239.59, as the issue is not seen on latest canary 64.0.3279.0 using Windows 10, Ubuntu 14.04 and Mac 10.12.6, hence providing reverse bisect info

Bisect Info:
================
Last bad build: 64.0.3267.0 Revision(516147)
First good build: 64.0.3268.0   Revision(515867)

You are probably looking for a change made after 516132 (known good), but no later than 516133 (first known bad)
CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/599b5bf5e68612a03f3af06304ae37c74ee19112..5b4a0cb6c9f73c4c27bddd6909706452cf2cd47e

Probably fixed by: https://chromium-review.googlesource.com/590273

@Avi Drissman: Please confirm the issue and help in merging this issue to M-62 and M-63 if applicable

Thanks!

Comment 2 by a...@chromium.org, Nov 28 2017

Mergedinto: 96041
Status: Duplicate (was: Assigned)
This was fixed in M64.

An incorrect fix for this was removed in M62, which hid this problem. The real fix that's in M64 is too complicated for merging.
►

Sign in to add a comment