Provide a mechanism to the decl. WebRequest API to match URLs without the query against a RegEx

chrome/common/extensions/api/events.json

Index: chrome/common/extensions/api/events.json
diff --git a/chrome/common/extensions/api/events.json b/chrome/common/extensions/api/events.json
index d28eb9358b4568cbfbb6f55a0218163e9a059064..d7e7e371f917dc8182cadf99612d6e5b271524fe 100644
--- a/chrome/common/extensions/api/events.json
+++ b/chrome/common/extensions/api/events.json
@@ -271,6 +271,11 @@
             "description": "Matches if the URL (without fragment identifier) matches a specified regular expression. Port numbers are stripped from the URL if they match the default port number. The regular expressions use the <a href=\"http://code.google.com/p/re2/wiki/Syntax\">RE2 syntax</a>.",
             "optional": true
           },
+          "strippedUrlMatches": {

[Yoyo Zhou, 2013/04/08 18:20:43]

This is not my favorite name but I can't think of a better one. RFCs call this
the "hierarchical part" but that name is less understandable.

[battre, 2013/04/09 12:22:23]

Discussed this with Jeffrey and we concluded that originAndPathMatches might
work.

+            "type": "string",
+            "description": "Matches if the stripped URL (without query segment and fragment identifier) matches a specified regular expression. Port numbers are stripped from the URL if they match the default port number. The regular expressions use the <a href=\"http://code.google.com/p/re2/wiki/Syntax\">RE2 syntax</a>.",
+            "optional": true
+          },
           "urlPrefix": {
             "type": "string",
             "description": "Matches if the URL (without fragment identifier) starts with a specified string. Port numbers are stripped from the URL if they match the default port number.",