New issue
Advanced search Search tips

Issue 814661 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression
Team-Security-UX



Sign in to add a comment

Regression:Sound icon doesn't appear in omnibox after reloading the manually crash page.

Reported by vku...@etouch.net, Feb 22 2018

Issue description

Chrome Version:66.0.3352.0 (Official Build) db148559378834dcddbc7066d6f899b5e227d426-refs/heads/master@{#538313}(32/64-bit) 
OS:Windows (7,8,8.1,10), Mac(10.12.6, 10.13.1, 10.13.4), Linux(14.04 LTS)

What steps will reproduce the problem?
(1)Launch chrome and navigate to http://christmasgifts.trzn.com/
(2)Click on 'view site info' lock icon > Select 'Block' under Sound option such that sound icon appears in omnibox.
(3)Manually crash the page via chrome://kill, now reload the page and observe the sound icon in omnibox.

Actual: Sound icon doesn't appear in omnibox after reloading the manually crash page.

Expected: Sound icon should appear in omnibox after reloading the manually crash page.

This is a regression issue broken in 'M65' and below is the manual bisect info
Good Build: 65.0.3305.0 (Revision:526189)
Bad Build:  65.0.3306.0 (Revision:526248)

Note: This issue is also seen on M66 Dev(build #66.0.3346.8).

 
Actual_Sound.mp4
4.5 MB View Download
Expected_Sound.mp4
3.5 MB View Download

Comment 1 by vku...@etouch.net, Feb 22 2018

Labels: hasbisect-per-revision RegressedIn-65 FoundIn-66 Target-66 Target-65 FoundIn-65
Owner: mlamouri@chromium.org
Status: Assigned (was: Unconfirmed)
You are probably looking for a change made after 526240 (known good), but no later than 526241 (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/be45e8e1e3924a788ff72dcc5ecb6ef8264ebe8a..12c615ca3716162f32341c597d581b3a6d6b7f95

Suspect: https://chromium.googlesource.com/chromium/src/+/12c615ca3716162f32341c597d581b3a6d6b7f95

@mlamouri: 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.
                                                                                                                                                                                            
Status: WontFix (was: Assigned)
Thanks for the report :)

Given the CL that marked as suspect, this is most likely because this website was autoplaying on page load and we are blocking autoplay. That means that the website no longer makes sound and therefore, Chrome no longer shows that the sound is blocked.

TL;DR: Wroking As Intended.

Sign in to add a comment