New issue
Advanced search Search tips

Issue 913656 link

Starred by 2 users
Status: Duplicate
Merged: issue 896550
Owner:
ellyjo...@chromium.org
Closed: Dec 12
Cc:
viswa.karala@chromium.org
mac-bugs-priority@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Back/forward popup menu does not display ampersands in titles

Reported by kpreid.s...@gmail.com, Dec 10 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36

Steps to reproduce the problem:
1. Visit a web page with an "&" ampersand in the title (correctly escaped in the HTML) such as https://music.stackexchange.com/ or https://switchb.org/kpreid/topics/sim
2. Visit another page, so the previous page is available in the back button popup menu.
3. Click and hold on the back button popup menu.

What is the expected behavior?
The menu displays the "&" in the title text.

What went wrong?
The "&" is not displayed.

Did this work before? N/A 

Chrome version: 71.0.3578.80  Channel: stable
OS Version: OS X 10.14.1
Flash Version: 

I found mention of previous trouble with & in the history menus: https://bugs.chromium.org/p/chromium/issues/detail?id=17660

Comment 1 by vamshi.kommuri@chromium.org, Dec 11

Labels: Needs-Triage-M71

Comment 2 by viswa.karala@chromium.org, Dec 11

Cc: viswa.karala@chromium.org
Labels: Needs-Bisect Triaged-ET
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on chrome reported version# 71.0.3578.80 with steps mentioned in comment# 0 using Mac 10.12.6. Issue is not seen on latest chrome# 73.0.3636.0. Working on bisect info, will update the other OS behaviour and bisect info soon. Hence marking this issue as Untriaged and adding Needs-Bisect label to it.

Thanks!

Comment 3 by viswa.karala@chromium.org, Dec 12

Components: -UI UI>Browser
Labels: -Type-Bug -Pri-2 -Needs-Bisect hasbisect-per-revision RegressedIn-70 Target-71 M-71 FoundIn-71 Pri-1 Type-Bug-Regression
Owner: ellyjo...@chromium.org
Status: Assigned (was: Untriaged)
Able to reproduce the issue on reported version 71.0.3578.80 and the same is not seen on latest chrome# 73.0.3637.0 and Dev# 72.0.3626.14 using Mac 10.12.6 hence providing reverse bisect info

Reverse Bisect Info:
================
Last Bad build: 72.0.3588.0
First Good build: 72.0.3589.0

You are probably looking for a change made after 601743 (known good), but no later than 601744 (first known bad).
https://chromium.googlesource.com/chromium/src/+log/8657d868e6ce3e114b843844ecbed67133068f1c..f8b6b9dc2e636fdc5d3333c4dae832ff1a9baad6
Change-Id: I83f6bc6f5b71efa1d7220d8d20afa7dd833771ba
Reviewed-on: https://chromium-review.googlesource.com/c/1287325

@Elly Fong-Jones: Please confirm the issue and help in re-assigning if it is not related to your change, Please help in merging it to M-71 if applicable.
Adding ReleaseBlock-Stable for M-71, feel free to remove it if not applicable.

Thanks!

Comment 4 by viswa.karala@chromium.org, Dec 12 

Correction to C# 3:
Not adding any blocker for M-71 as it got regressed in M-70.

Comment 5 by ellyjo...@chromium.org, Dec 12

Mergedinto: 896550
Status: Duplicate (was: Assigned)
Yes, the linked change fixed this exact bug - 896550 on that CL is this bug.
►

Sign in to add a comment