I must have done something to Google Chrome on my Mac.

Local HTML files, even though they are associated with Chrome, do not actually open in Chrome anymore. For example, double clicking an HTML file on my desktop will launch Chrome, but the browser window will not display the content of the HTML file.

If I change the program my computer will use to display HTML files to Safari or Firefox, they open as I expect them to, rendering the HTML properly in a browser window.

If, I have a Chrome window open and drag the HTML file into the browser window, it will render the HTML content properly, but the double clicking is the behavior I'm hoping to get back.

Does anyone know why this might have caused this change in Chrome behavior? And best of all, how to fix it?

Chrome extensions I use: LastPass, Xmarks, Google Voice.

link|improve this question
feedback

migrated from stackoverflow.com Mar 15 '11 at 10:37

This question came from our site for professional and enthusiast programmers.

2 Answers

The OS assumes that a file association just means "appname" "filename.ext". If for some reason the people over at Google screwed that up somewhere that would be a reason why it stopped working

link|improve this answer
feedback

This seems to be a bug in Chrome, it's been reported to Google, so we can just sit and wait for them to fix it. No workaround at the moment that I know of...

link|improve this answer
feedback

Your Answer

 
or
required, but never shown