Issue metadata
Sign in to add a comment
|
Opening a local file results in a blank tab
Reported by
oli...@oliverdunk.com,
Nov 7 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Get your Mac into the broken state. I'm not sure how to do this. 2. Open a local file from either your desktop or Finder. What is the expected behavior? The file which was opened in Chrome is displayed What went wrong? Rather than seeing the file, a blank page is shown instead Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? Yes Does this work in other browsers? Yes Chrome version: 62.0.3202.89 Channel: stable OS Version: OS X 10.13.0 Flash Version: Have spoken to a few other people who have had this issue. It seems that restarting Chrome or your Mac is a fix. As a workaround, dragging the local file directly into Chrome as a new tab seems to work.
,
Nov 7 2017
> 2. Open a local file from either your desktop or Finder. A local file being a PDF? With Chrome set as the default app for opening PDFs?
,
Nov 7 2017
I am afraid that I was also able to reproduce this with HTML and JPEG files.
,
Nov 8 2017
Unable to reproduce the issue on mac 10.13 high sierra using chrome reported version #62.0.3202.89. Attached a screen cast for reference. Following are the steps followed to reproduce the issue. ------------ 1. Opened a pdf file and a jpeg file in chrome browser. 2. Observed that both files rendered without any issues. Reporter@ - Could you please check the screen cast and please let us know if anything missed from our side. Also please check the issue on a clean profile without any apps and extensions and please let us know if the issue still persists or not. Thanks...!!
,
Nov 8 2017
It does appear that you did everything correctly in the video. There's some sort of broken state that Chrome gets into for this to happen, and I haven't yet been able to work out the steps to break Chrome on demand. I've spoken to multiple people with this issue, but if there's no immediately obvious cause, I can simply comment back here when I learn more?
,
Nov 8 2017
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 8 2017
Are there any messages in the Console when this failure occurs?
,
Nov 8 2017
Sadly, I haven't been able to reproduce the issue since I opened this bug to check. I'll keep an eye out and check in dev tools next time it happens, though. If I do reproduce the issue, is there any sort of report that I can take which will be useful for debugging?
,
Nov 8 2017
Thank you for providing more feedback. Adding requester "shrike@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 9 2017
Thanks for the report. As you don't see the issue for now, we are closing this as WontFix. If this reproduces, feel free to reopen (change the status to available) with the reproduction steps. Especially, > 1. Get your Mac into the broken state. I'm not sure how to do this. is not a good description how to reproduce. If your Mac is in a broken state, anything can be broken :)
,
Nov 9 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by manoranj...@chromium.org
, Nov 7 2017Labels: Needs-Triage-M62