diff options
| author | battre@chromium.org <battre@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-08-25 20:32:08 +0000 |
|---|---|---|
| committer | battre@chromium.org <battre@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-08-25 20:32:08 +0000 |
| commit | 815d5f4e41b1ea064b090efad24d9cf8dca21776 (patch) | |
| tree | b11c2e0ab184aded6f0fcf34fb6f3c7de4d29184 /chrome/browser/ui/profile_menu_model.cc | |
| parent | 4e6c61f7ee7caffbc7639ccf00f809d477e4eb68 (diff) | |
| download | chromium_src-815d5f4e41b1ea064b090efad24d9cf8dca21776.zip chromium_src-815d5f4e41b1ea064b090efad24d9cf8dca21776.tar.gz chromium_src-815d5f4e41b1ea064b090efad24d9cf8dca21776.tar.bz2 | |
Fix mismatch about tabId in code and webrequest API documentation if requests don't belong to a tab
This CL updates the webrequest API documentation to state that requests that cannot be associated with a tab are labeled with "tabId = -1" instead of "tabId = null".
I chose to update the documentation rather than the code for two reasons:
- As 0 is a valid value for the tabId, we would need to distinguish between 0 and null.
- For the RequestFilter type, 'tabId' is an optional parameter. I.e. we would need to distinguish between 0, null and undefined.
BUG=93373
TEST=no
Review URL: http://codereview.chromium.org/7741014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@98289 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/ui/profile_menu_model.cc')
0 files changed, 0 insertions, 0 deletions