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

Issue 789834 link

Starred by 2 users
Status: Fixed
Owner:
steimel@chromium.org
Closed: Dec 2017
Cc:
nyerramilli@chromium.org
rbasuvula@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug
Team-Security-UX



Sign in to add a comment

Sound block icon doesn't appear after blocking sound from site settings page.

Reported by vku...@etouch.net, Nov 30 2017 
Chrome Version: 64.0.3280.0 (Official Build)Revision 12d6a1a2daf69e7fed839a65b0d1284021056b6a-refs/heads/master@{#519958} (32/64-bit)
OS: Win(7,8,10),Mac(10.12.6,10.13.2),Linux(14.04 LTS).

What steps will reproduce the problem?
(1)Freshly launch chrome browser and navigate to http://tidbits.com/podcasts/14397.m4a
(2)Click 'view site info' button > site settings > sound > select block.
(3)Switch to previous tab, observe the block icon and now click on 'reload' button of info bar,observe.
 
Actual: Sound block icon doesn't appear(stay) after blocking sound from site settings page.

Expected: Sound block icon should appear in omnibox after blocking sound from site settings page.

This is a Non-regression issue seen from 'M64' series i.e from build no. 64.0.3248.0
Actual_Sound.mp4
715 KB View Download

Comment 1 by rbasuvula@chromium.org, Nov 30 2017

Status: Untriaged (was: Unconfirmed)
As this being a Non-Regression issue, changing the status to Untriaged so that the issue would get addressed.

Thank You!

Comment 2 by mpear...@chromium.org, Dec 13 2017

Components: -UI>Settings UI>Browser>Permissions>Prompts
This has something to do with permissions, labeling as such.  Please re-label if I guessed wrong.

Comment 3 by raymes@chromium.org, Dec 13 2017

Components: -UI>Browser>Permissions>Prompts UI>Browser>Permissions>Indicators
Owner: steimel@chromium.org
Status: Assigned (was: Untriaged)
steimel: could you ptal?

Comment 4 by steimel@chromium.org, Dec 14 2017

Status: Started (was: Assigned)

Comment 5 by steimel@chromium.org, Dec 16 2017

Status: Fixed (was: Started)
This was fixed with Revision a79f734269fecea8cc69f7982ae68b66ce510608 (crrev.com/c/738198). I believe that happened after the M64 branch, but I don't think it's a big enough issue to patch into M64
►

Sign in to add a comment