New issue
Advanced search Search tips

Issue 702714 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 547953
Owner:
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Desktop media picker UI behaves differently on Mac than Windows

Reported by joshbfre...@gmail.com, Mar 17 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. Open up the Desktop media picker UI in chrome on a windows machine

What is the expected behavior?

What went wrong?
The picker UI behaves differently than it does on a mac. On mac the picker UI is a different window and on windows it is inside the window. This causes a problem if the window is small to begin with. 

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 56.0.2924.87  Channel: n/a
OS Version: OS X 10.11.6
Flash Version: Shockwave Flash 25.0 r0

Due to this we are getting a different experience for our customers with our product. On mac the picker acts a separate window and so the user can move it out of the way or type into the chat client we provide asking questions. On Windows they no longer can type while the picker is up and also if the screen is small it will become a weird UI. What I would like to see if that on windows the picker UI pops out into a different window like mac that way the UX can be the same for both windows and mac.
 
Labels: Needs-Milestone

Comment 2 Deleted

Comment 3 Deleted

First time writing up a bug here. What do you mean by milestones? Is this something I need to provide you with?

Comment 5 by ajha@chromium.org, Mar 21 2017

Components: -Blink>GetUserMedia Blink>GetUserMedia>Desktop
Thanks for filing this & nothing required from your end as of now. Adding respective component for someone from the respective team to take a look at this.
Owner: qiangchen@chromium.org
Qiang, I assume there's reasons for this, can you comment?
Mergedinto: 547953
Status: Duplicate (was: Unconfirmed)
The chrome UI foundation does not wrap Mac API into the basic chrome UI component. So when we make a specific UI for some dialog window, we directly use those Mac standard component, which looks different from chrome standard component.

I heard that the UI team is doing migration last year, but so far I did not see any change yet. Merge this issue into the main one.

Sign in to add a comment