Save As dialog is not shown when running inside docker through Xvfb
Reported by
andrjoos...@gmail.com,
Sep 14 2016
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.113 Safari/537.36 Steps to reproduce the problem: Hi, we are running Chrome inside docker using one of official selenium images: docker run -d -p 4444:4444 selenium/standalone-chrome:latest They are using Xvfb to run Chrome. We have a test which opens chrome://webrtc-internals page and clicks on "Enable event log recording" and then make a WebRTC call from another tab. Clicking on "Enable event log recording" should trigger Save As dialog (which we used to close via sending a return keycode to main Chrome window). What is the expected behavior? Save As dialog is opened and event log files can be found in Downloads directory What went wrong? Looks like dialog is not opened at all - there are no event log files Did this work before? Yes Everything worked in Chrome 49 Chrome version: 53.0.2785.101 Channel: stable OS Version: Ubuntu 16.04 on Linux 4.1.19-boot2docker Flash Version: Not sure Interesting that it works when I run the same test in selenium debug image: docker run -d -p 4444:4444 selenium/standalone-chrome-debug:latest The only difference between debug and non-debug images is that the first has built-in VNC server and window manager (fluxbox)
,
Sep 14 2016
Thanks for the description. Changed it from DevTools -> WebRTC because this isn't actually a part of DevTools.
,
Sep 15 2016
Looks like this issue can't triaged from TE end, added TE-NeedsTriageHelp to further investigate.
,
Sep 16 2016
[triage]: Bug with webrtc-internals UI. Not sure who owns this; grunell, can you help with an owner?
,
Sep 16 2016
I believe guidou@ owns this. Guido, let me know if that's not true.
,
Mar 22 2017
Any chance that this is a generic issue with the SaveAs dialog?
,
Oct 7 2017
Making this available since I do not plan on working on this any time soon.
,
Oct 8
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 12
andrjooshka@: do you know if this is still an issue?
,
Oct 12
Unfortunately I can't confirm if it is still an issue or not
,
Oct 12
OK, thanks for the information. Closing. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by andrjoos...@gmail.com
, Sep 14 2016