Drive by, given the status of the bug:
This works as intended, as the page has left the custody of the device/chrome.

For comment #2, we do support this scenario since we can verify the file via digest.

I can't repro this with 6.0.1. Can anyone repro this?

I could not repo this with 8.1.0 (device A) and dogfood of P (device B).

IIRC, during the bug bash I shared this with petewil@ and his device was running KitKat. 

To be specific, the A device was dogfood P, and the B device was KitKat (4.4.1)

I tried this with device A as Android Nougat and device B as Oreo, it did not repro.

I tried using the original device B, but it is broken now, and I was unable to get ShareIt to send the file back.  I tried this with another KitKat phone, but it was unable to use ShareIt with the Nougat phone.

I found a way to repro this after all, going from  Nougat to KitKat - the missing step is to first send a file from KitKat to Nougat to establish the WiFi connection, then do the rest of the repro steps.

Looks like the problem is that there is a "!" in the file: url, and MimeTypeMap.getFileExtensionFromUrl is considering it a non-valid URL, and refusing to return the "mhtml" at the end, so this is not looking like a MHTML file. 

https://chromium-review.googlesource.com/c/chromium/src/+/1033482 landed to fix this.

We would like to merge the fix, which is basically just checking offline pages file extension differently.

The change is to look for the file extension as everything after the last dot instead of excluding all filenames with characters that might be legal for files but are not legal for urls, and then looking for the last dot.

This bug requires manual review: M67 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), kbleicher@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

has the fix been verified in canary?

Thanks for getting back to me!

The fix was not in this morning's canary.  It went in about 5pm yesterday, not sure when the canary syncs.
I also didn't see a fix from Tuesday in this morning's canary, so I wonder when Canary synced last.

I'll try again with tomorrow's canary.

Verified in today's canary.

I hope this merge is safe for M67.

This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot