Re: Issue 126955 in chromium: Chrome can't open MHTML file directly

[chro...@googlecode.com]

Comment #33 on issue 126955 by gspe...@chromium.org: Chrome can't open
MHTML file directly
http://code.google.com/p/chromium/issues/detail?id=126955

The WebKit patch has been committed, so we're just waiting until it
trickles down, and this issue should be fixed.

[chro...@googlecode.com]

Comment #35 on issue 126955 by gspe...@chromium.org: Chrome can't open

MHTML file directly
http://code.google.com/p/chromium/issues/detail?id=126955

OK, the webkit patch has arrived in our tree, but this still doesn't seem
to work, so I need to see why.

[chro...@googlecode.com]

Comment #42 on issue 126955 by zeli...@chromium.org: Chrome can't open

MHTML file directly
http://code.google.com/p/chromium/issues/detail?id=126955

is this fully fixed now? if so, please mark bug as fixed

[chro...@googlecode.com]

Updates:
Status: Verified

Comment #44 on issue 126955 by bhaves...@chromium.org: Chrome can't open

MHTML file directly
http://code.google.com/p/chromium/issues/detail?id=126955

Verified on 22.0.1208.0

[chro...@googlecode.com]

Updates:
Status: Started

Comment #48 on issue 126955 by joshwood...@chromium.org: Chrome can't open

MHTML file directly
http://code.google.com/p/chromium/issues/detail?id=126955

I was contacted by a user that was having this issue. Here is how it was
described:

######
I can use the Google provided experimental flag to save a web page to an
MHT file, or do so from Firefox or IE.
And I can use Chrome to open to file and view it. Great, so far...

BUT... I cannot view MHT files from Google Drive... using v33.0.1750.146m
today nor (last I checked) on CHROMEBOOKS, where it is really a more
pressing issue.

patches have been tested to work:

Jul 17, 2012 #44 bhaves...@chromium.org
Verified on 22.0.1208.0

And then committed, per review:
https://chromiumcodereview.appspot.com/10559086

Is this just laying around, with no champion to request the committed
patch(es) to be picked up?
Or is there some other issue that I cannot seem to find that is blocking
this from being incorporated into release?

OR was this issue actually TWO issues - one to view MHT files directly in
Chrome, and another issue to view MHT files from GOOGLE DRIVE? And just the
fix for former was actually addressed in the above threads?

Regards and thanks.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Status: Verified

Comment #50 on issue 126955 by kin...@chromium.org: Chrome can't open MHTML
file directly
http://code.google.com/p/chromium/issues/detail?id=126955

Verified once again in M33-35 and it is working (opening MHTML from "Google
Drive" folder in Files.app just works.)

Josh, I think #49 is the case. Could you refer the user to Drive web UI
side (if appropriate?)

[chro...@googlecode.com]

Comment #51 on issue 126955 by joshwood...@chromium.org: Chrome can't open

MHTML file directly
http://code.google.com/p/chromium/issues/detail?id=126955

Thanks!