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

Issue 777789 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Close 'x' button not working on thumbnails of Bing.

Reported by shruti.j...@etouch.net, Oct 24 2017

Issue description

Chrome Version: 64.0.3248.0 (Official Build)03ab3c4833605018d8bd5c2cd5efb94434450407-refs/heads/master@{#510988}(64-bit)

OS: Win(7,8,10), Mac(10.12.6) and Linux(14.04 LTS).


Steps to reproduce:
1.Launch chrome and Navigate to chrome://settings. 
2.Go to Search engine  and change it to Bing.
3.Visit some pages and open new Tab which shows Bing page having Thumbnails.
4.Click on 'x' button of thumbnails and observe.


Actual Result:  Close 'x' button not working on thumbnails of Bing.
Expected Result:  Close 'x' button  should work on thumbnails of Bing.

This is regression issue broken in ‘M-64’ and will soon update bisect-info

Using the per-revision bisect providing the bisect results,
Good Build: 64.0.3244.0(Revision:509945).
Bad Build: 64.0.3245.0(Revision:510270).





 
actualbing.mp4
605 KB View Download
expectededbing.mp4
531 KB View Download
Components: UI>Browser>NewTabPage
Labels: hasbisect-per-revision
Owner: treib@chromium.org
Status: Assigned (was: Unconfirmed)
Kindly refer the Bisect info:
You are probably looking for a change made after 510038 (known good), but no later than 510039 (first known bad).
CHANGELOG URL:
The script might not always return single CL as suspect as some perf builds might get missing due to failure.
  https://chromium.googlesource.com/chromium/src/+log/d54d7720c320abe789fa929ed9846474c699094e..06d66032b7347e23e4ff2f49a8692efc5ad07d1c

Suspect:https://chromium.googlesource.com/chromium/src/+/06d66032b7347e23e4ff2f49a8692efc5ad07d1c

@treib:Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thank You!
Labels: ReleaseBlock-Beta
Tagging with blocker label, please undo if not the case.

Comment 3 by treib@chromium.org, Oct 24 2017

Labels: OS-Chrome
Yup, that's mine. Turns out the Bing NTP passes the to-be-blacklisted ID as a string rather than an int, and Gin is more strict about that than the v8::Extension was.

Comment 4 by treib@chromium.org, Oct 24 2017

Status: Started (was: Assigned)

Comment 5 by mastiz@chromium.org, Oct 24 2017

Labels: zine-triaged
Project Member

Comment 6 by bugdroid1@chromium.org, Oct 24 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7d0633dde4a03e0cf3411a04554e73559c835095

commit 7d0633dde4a03e0cf3411a04554e73559c835095
Author: Marc Treib <treib@chromium.org>
Date: Tue Oct 24 15:23:35 2017

embeddedSearch API: Be less strict with argument types

The API functions deleteMostVisitedItem and undoMostVisitedItemDeletion
need an int parameter, but are called with int-inside-a-string by
third-party NTPs. This was legal with the old v8::Extension
implementation, but the Gin implementation from crrev.com/c/700443 is
stricter.
This CL relaxes the implementation so that strings that can be converted
to int are allowed again.

Bug:  777789 
Change-Id: I784973ad7bb3626ff58c0d6831053a93e00a8016
Reviewed-on: https://chromium-review.googlesource.com/735608
Commit-Queue: Marc Treib <treib@chromium.org>
Reviewed-by: Chris Pickel <sfiera@chromium.org>
Cr-Commit-Position: refs/heads/master@{#511152}
[modify] https://crrev.com/7d0633dde4a03e0cf3411a04554e73559c835095/chrome/browser/ui/search/local_ntp_browsertest.cc
[modify] https://crrev.com/7d0633dde4a03e0cf3411a04554e73559c835095/chrome/renderer/searchbox/searchbox_extension.cc

Comment 7 by treib@chromium.org, Oct 24 2017

Status: Fixed (was: Started)

Sign in to add a comment