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

Issue 615315 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner:
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Regression:Close/maximize/minimize buttons not functioning as expected in Enjoy Music Player app.

Project Member Reported by bj00129...@techmahindra.com, May 27 2016

Issue description

<b>Version: <Kenneth, what is the frequency?></b>
<b>OS: <please tell me it's not XP></b>

What steps will reproduce the problem?
(1)
(2)
(3)

What is the expected output?

What do you see instead?


Please use labels and text to provide additional information.

 
Cc: kavvaru@chromium.org ajha@chromium.org durga.behera@chromium.org
Components: Platform>Apps
Labels: -Type-Bug -Pri-3 Needs-Bisect M-52 OS-iOS OS-Windows Pri-1 Type-Bug-Regression
Status: Unconfirmed (was: Untriaged)
Summary: Regression:Close/maximize/minimize buttons not functioning as expected in Enjoy Music Player app. (was: Regression:)
Version:52.0.2743.11 
OS:Ubuntu 14.04,Windows

Test Url:https://chrome.google.com/webstore/detail/enjoy-music-player/hncfgilfeieogcpghjnnhddghgdjbekl/related?utm_source=chrome-ntp-icon

What steps will reproduce the problem?
(1)Launch chrome>> Go to above mentioned url>>Launch app>>Try to click on close/minimize/maximize and Observe

Expected:App should be closed/minimized/maximized when the respective icons are clicked.
Actual:Instead app remains idle.

This is a regression issue.Will update bisect info soon.

Actual_Apps.ogv
2.2 MB Download

Comment 2 by ajha@chromium.org, May 27 2016

Labels: -OS-iOS ReleaseBlock-Stable OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce this on the latest canary(53.0.2750.0) on Mac OS 10.11.4 as well.

Jahnavi@: Please update the bisect information here.
Labels: -Needs-Bisect hasbisect
Owner: yukishiino@chromium.org
Status: Assigned (was: Untriaged)
Good build:51.0.2680.0 Dev
Bad Build:51.0.2681.0 Dev

CHANGELOG URL:  https://chromium.googlesource.com/chromium/src/+log/689dc0e45d16789f3ce3241d3033601af395c313..607c6e18aae50211a534f964ebfdac47cdbf21be

Suspecting https://codereview.chromium.org/1667653002 from changelog.

@yukishiino: Please help reassigning if it is not related to your change.



Comment 4 by ajha@chromium.org, May 27 2016

Labels: -M-52 M-51
Regressed in M-51 hence adjusting the milestone.

Though there have been no instances of such issues on any other apps reported till now, still keeping the RB-stable label for M-51 to be considered for next stable refresh.

yukishiino@: Please take a look and adjust the milestone if you feel this isn't blocking for M-51.

Comment 5 by gov...@chromium.org, May 27 2016

Cc: pbomm...@chromium.org
This bug has been reported as M51 Stable blocker. We're cutting M51 Stable RC on Tuesday, May 31st @ 1:00 PM PST. pls make sure to land the fix and get it merged before then. 
Labels: -Pri-1 Pri-3
Status: WontFix (was: Assigned)
This issue seems caused by the app itself.  Other apps are working just fine, and this app is handling the mousedown events in their own way.  Plus, I see some unstable code in the app.

Before reopen this issue, please prepare the minimized repro case.

Sign in to add a comment