A few versions ago, Chrome broke the viewing of javadocs from the local file system. Well, not javadocs exactly, but any set of pages using a frameset that exists on the local file system. I generally download javadoc files for the various packages I'm working with. Having them local means I can access them even if my laptop is disconnected. What broke was that rather than having the links in the left side open in the main frame, Chrome opens them in a new tab, which is real annoying since all the navigation for the frameset is not on the new tab. I ended up going back to Firefox for most browsing just because of this bug.
This bug was first reported to Google in early April, and still isn't fixed. There has been a lot of discussion on various news groups and in
the bug itself. A fix is being worked on, but in the bug there is a reference to a command-line option that will work in the mean time. Start Chrome like this:
/usr/bin/google-chrome --allow-file-access-from-files
In Ubuntu, I have Chrome on the quick-launch bar, so I just right clicked on the icon, selected properties, and pasted this line into the "command" box.
No comments:
Post a Comment