[Offline Page]Making mhtml file recognized as openable by Chrome

chrome/android/java/AndroidManifest.xml

 <?xml version="1.0" encoding="utf-8"?>
 <!-- Copyright 2015 The Chromium Authors. All rights reserved.
      Use of this source code is governed by a BSD-style license that can be
      found in the LICENSE file. -->
 
 <!--
 Note: This is a jinja2 template, processed at build time into the final manifest.
 
 Blocks denoted with { % block some_name % }foo{ % endblock % } can be overridden
 by a child template that "extends" this file.
@@ skipping 169 matching lines @@
                 <data android:scheme="about" />
                 <data android:scheme="content" />
                 <data android:scheme="javascript" />
                 <data android:mimeType="text/html"/>
                 <data android:mimeType="text/plain"/>
                 <data android:mimeType="application/xhtml+xml"/>
             </intent-filter>
             <!-- MHTML support, used for snapshots -->
             <intent-filter>
                 <action android:name="android.intent.action.VIEW" />
                 <category android:name="android.intent.category.DEFAULT" />

[Ted C, 2016/07/26 17:01:47]

seems odd that this is the one VIEW handler that lacks BROWSABLE...any idea why
that is?

[Vivian, 2016/07/26 17:12:59]

Not really sure about this...seems like this piece of code was there from the
very beginning.

-                <data android:scheme="file" android:mimeType="multipart/related"/>
+                <data android:mimeType="multipart/related"/>

[Ted C, 2016/07/26 17:01:47]

why did this drop the file restriction?  I see in the bug comment that this
handles certain cases, but what are the schemes that are used in those?

[Vivian, 2016/07/26 17:12:59]

Google Drive, Gmail and Android's Download use content scheme.

[Ted C, 2016/07/26 17:17:09]

Should we specify file || content then like the below filters?

[Vivian, 2016/07/26 17:21:37]

In Android's developer guide
(https://developer.android.com/guide/topics/manifest/data-element.html) it says:
"If the filter has a data type set (the mimeType attribute) but no scheme, the
content: and file: schemes are assumed."
But I guess specifying the schemes would make it less confusing.

[Ted C, 2016/07/26 17:24:02]

Ah, didn't know that.  Not sure whether it is worth specifying then.  It is nice
for clarity, but that is only because I'm not intimately familiar with
intent-filters.

[Vivian, 2016/07/26 17:41:31]

Uploaded a new patch, making the schemes explicit.

+            </intent-filter>
+            <intent-filter>
+                <action android:name="android.intent.action.VIEW" />
+                <category android:name="android.intent.category.DEFAULT" />
+                <category android:name="android.intent.category.BROWSABLE" />
+                <data android:scheme="file"/>
+                <data android:scheme="content"/>
+                <data android:host="*" />
+                <data android:pathPattern=".*\\.mhtml"/>
+                <data android:pathPattern=".*\\.mht"/>
+                <data android:pathPattern=".*\\.eml"/> 
+            </intent-filter>
+            <intent-filter>
+                <action android:name="android.intent.action.VIEW" />
+                <category android:name="android.intent.category.DEFAULT" />
+                <category android:name="android.intent.category.BROWSABLE" />
+                <data android:scheme="file"/>
+                <data android:scheme="content"/>
+                <data android:host="*" />
+                <data android:mimeType="*/*"/>
+                <data android:pathPattern=".*\\.mhtml"/>
+                <data android:pathPattern=".*\\.mht"/>
+                <data android:pathPattern=".*\\.eml"/> 
             </intent-filter>
             <intent-filter>
                 <action android:name="android.intent.action.MEDIA_SEARCH" />
                 <category android:name="android.intent.category.DEFAULT" />
             </intent-filter>
             <intent-filter>
                 <action android:name="android.speech.action.VOICE_SEARCH_RESULTS" />
                 <category android:name="android.intent.category.DEFAULT" />
             </intent-filter>
             <intent-filter>
@@ skipping 652 matching lines @@
              choose the first MediaRouteController that can play it, so the order of the list can be important.
              The most specific MediaRouteControllers should be listed first, followed by more generic ones.
              The downstream manifest replaces this block, and hence replaces the list of media route
              controllers with its own list. -->
         <meta-data android:name="org.chromium.content.browser.REMOTE_MEDIA_PLAYERS"
             android:value="org.chromium.chrome.browser.media.remote.DefaultMediaRouteController"/>
 
         {% endblock %}
     </application>
 </manifest>