@janne.granstrom : Janne, this is likely due to https://blog.google/products/chrome/flash-and-chrome/.

to get it working again do the following:
1. yclick on the green lock to the left of https://olay.spotify.com. 
2. Look down to Flash, and click on Ask, choose "Allow"
3. click the reload button when it shows.

then follow the other directions Spotify indicates in https://community.spotify.com/t5/Web-Player/Spotify-WebPlayer-fails-and-prompts-for-Flash/m-p/1470698/highlight/true#M10074 if needed after the reload.

can you tell us if this works for you? 

No it not work, just take your time and read the issue.

I spent some time looking around the play.spotify.com interface after signing in and couldn't find an option to "Open spotify in windowed mode". There is an option to Play open.spotify.com URL's in desktop app under account options. 

is this an option only for Premium accounts? Could you tell us how to get to open the web player in windowed mode so we can try to reproduce your issue? Thank you for your help.

Really?

If you are a developer of Chromium,  how you not know how to make a window
mode shortcut of a web page,  i mean any web page?

Ok.
1. Open play.spotify.com
2. Then open a browser options menu (three dots button)
3. Go to More tools > Add to desktop
4. check Open as a window.
5. Now you have a shortcut icon in your desktop which open that url in
window mode (chrome without any browser elements on it).

19.11.2016 1.35 ap. "eri… via monorail" <monorail+v2.840917497@chromium.org>
kirjoitti:

janne: Cool I had no idea you could do that (opening a window mode shortcut).

In M56, you both have to Allow plugins using the green lock to the left of the URL, and also choose "Run all plugins this time". See the screenshot.

But with the Window Mode spotify, there is no Omnibox, so there's no place to click "Run all plugins this time"...

Does that accurately reflect the problem?

Also - does it work in non-Window mode?

Deleted: Screenshot from 2016-11-18 16:12:29.png 30.5 KB

	Screenshot from 2016-11-18 16:12:29.png 30.5 KB View Download

yes, that is the problem.

I cannot allowing flash to run because of the address bar (omni).

I also have rules/premissions in the chrome settings allowing it to run flash or anything else on *.spotify.com domain but chrome dosnt see it at all.

Even when i go to spotify directly from the chrome (normal browser mode) the plugin is blocked, only way to get Spotify to load is use that "run all plugins this time".

i try to allow adobe flash plugin load automaticly when chrome starts (from chrome://plugins), but that isnt the case and not helped on this bug.

the problem is that chrome just not see these rules what i have for plugins (where they can run and not can).

You can see that flash rule option window in a attachment.

Deleted: flash.png 63.0 KB

	flash.png 63.0 KB View Download

Hey janne:

I think I "get you" now. You're wondering: I have spotify on my exception list. Why is it still broken?

The answer: For M56, we're currently testing blocking tiny cross-origin plugin content *even in ALLOW mode*. You will have to use the Omnibox icon to play those tiny cross-origin plugins even in ALLOW mode.

It seems that this is confusing behavior in some cases... and when the browser is in Omnibox-less Window Mode, there is no way to play Tiny plugins.

We will have to think about this... Thank you for your feedback!

Deleted: Screenshot from 2016-11-18 16:12:29.png 30.5 KB

	Screenshot from 2016-11-18 16:12:29.png 30.5 KB View Download

tommycli@chromium.org: Note when there's an enterprise policy that blocks flash there's another layer where that option is blocked.  I.e. in the presence of an enterprise policy controlling flash there's no mechanism to proceed.

See the attached image (and if we restrict view this I have more details).

Thanks!!!

Deleted: spotify.png 178 KB

	spotify.png 178 KB View Download

assigning to tommycli@ (after discussion with raymes, dominickn, & laforge). Proposal is as suggested by dominickn : when in windowed mode, if plugin is blocked, drop down omnibox & show current plugin-blocked (as is the case here since spotify plugin is both tiny & cross-origin). User will then be allowed to click on broken puzzle piece & run all plugins this time.

Any plans to address the enterprise policy bad interaction?  Should that be routed instead to a new bug?

Thanks!!

batz: We updated  issue 655899  which is about the UI changes that should be made so that should be the right place to follow along. The solution is to allow the "Run" button to be clicked even when enterprise policy is set to ASK.

Merging into root cause bug.