summaryrefslogtreecommitdiffstats
path: root/chrome/browser/extensions/extension_omnibox_api.cc
Commit message (Collapse)AuthorAgeFilesLines
* De-experimentalify omnibox extension API.mpcomplete@chromium.org2010-11-181-4/+4
| | | | | | | | | BUG=61547 TEST=covered by unit tests Review URL: http://codereview.chromium.org/5101001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66562 0039d316-1c4b-4281-b951-d872f2087c98
* More changes to extension omnibox API for styles.mpcomplete@chromium.org2010-11-161-48/+17
| | | | | | | | | | | | | - Overlapping styles are now bitwise-ORed together (instead of replacing previous ones). - The "length" parameter for style ranges is optional and can be 0. BUG=63077,63078 TEST=covered by tests Review URL: http://codereview.chromium.org/5064001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66327 0039d316-1c4b-4281-b951-d872f2087c98
* Revise the omnibox extension API so that specifying descriptionStyles is easier.mpcomplete@chromium.org2010-11-111-41/+81
| | | | | | | | | | | | Now each style has a range that it applies to. The styles can also overlap and be listed out of order. BUG=62385 TEST=covered by unit/browser tests Review URL: http://codereview.chromium.org/4660008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65869 0039d316-1c4b-4281-b951-d872f2087c98
* Coverity: Initialize member variables.jhawkins@chromium.org2010-10-271-1/+1
| | | | | | | | | | CID=13467,13487,13488 BUG=none TEST=none Review URL: http://codereview.chromium.org/4122001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64166 0039d316-1c4b-4281-b951-d872f2087c98
* Part 2 of extension event refactor.mpcomplete@chromium.org2010-10-211-5/+2
| | | | | | | | | | | | | Extension events are no longer broadcast to an entire process. They are filtered by extension. This allows me to move the cross-incognito check into the browser, and remove a bunch of cruft associated with that. BUG=58214 TEST=no functional change Review URL: http://codereview.chromium.org/3775015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63448 0039d316-1c4b-4281-b951-d872f2087c98
* FBTF: Even more deinlining.erg@google.com2010-10-201-0/+9
| | | | | | | | | BUG=none TEST=compiles Review URL: http://codereview.chromium.org/3879002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63261 0039d316-1c4b-4281-b951-d872f2087c98
* Pull events-related code out of ExtensionMessageService into its own class.mpcomplete@chromium.org2010-10-151-7/+7
| | | | | | | | | | | | | | The events code is independent of the messaging code and didn't belong in the same class. This is part 1 of an extension event refactor. See bug for more details. BUG=58214 TEST=covered by tests Review URL: http://codereview.chromium.org/3758005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@62764 0039d316-1c4b-4281-b951-d872f2087c98
* Add support for a "split" incognito behavior for extensions.mpcomplete@chromium.org2010-08-311-8/+4
| | | | | | | | | | | | | | | | - On by default for apps, off by default for extensions. - Split mode means "run incognito extensions in a separate process if the user says OK, and the two processes can only see their own profile." - Spanning mode is what we have now, and means "run a single extension process, but allow it to access both profiles if the user says OK." BUG=49232 BUG=49114 TEST=extensions still work in incognito when you check "Allow in Incognito". Review URL: http://codereview.chromium.org/3210007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58033 0039d316-1c4b-4281-b951-d872f2087c98
* Rename GetStringAsUTF16() to GetString() (and overload), etc.viettrungluu@chromium.org2010-08-041-7/+7
| | | | | | | | | | | | Also do some drive-by wstring/wchar_t -> string/char changes (in addition to the necessary ones). BUG=none TEST=builds and tests pass Review URL: http://codereview.chromium.org/3091005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@54944 0039d316-1c4b-4281-b951-d872f2087c98
* Add chrome.experimental.omnibox.styleUrl for highlighting text as an URL.mpcomplete@chromium.org2010-07-141-0/+1
| | | | | | | | | | | Update the chrome code search sample extension to have some fancier highlighting. TEST=none Review URL: http://codereview.chromium.org/2944012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@52358 0039d316-1c4b-4281-b951-d872f2087c98
* Add support for omnibox.onInputStarted and onInputCancelled.mpcomplete@chromium.org2010-07-021-7/+32
| | | | | | | | | | | | Also fix a bug where we'd keep an extension's old keyword even if it changed on upgrade/reload. BUG=46475 BUG=48091 Review URL: http://codereview.chromium.org/2807033 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@51540 0039d316-1c4b-4281-b951-d872f2087c98
* Address some visual problems with the omnibox extension API:mpcomplete@chromium.org2010-06-211-5/+76
| | | | | | | | | | | | - Remove some of the boilerplate strings. - Allow the description field to be fully customizable and stylable. BUG=46478 BUG=46479 Review URL: http://codereview.chromium.org/2849015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@50411 0039d316-1c4b-4281-b951-d872f2087c98
* First pass at experimental omnibox API. There are plenty of rough edges and ↵mpcomplete@chromium.org2010-05-281-0/+67
features to work on, but it's in a usable state. When an extension is installed that specifies an omnibox keyword in its manifest, we add that keyword to the user's list of Search Engines. The user can then edit this keyword later. I'm leveraging most of the original search engine keyword code. An extension keyword has a special URL that identifies it as an extension keyword. There is some special case code to treat these keywords slightly differently throughout the omnibox code. BUG=38884 Review URL: http://codereview.chromium.org/2078021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@48503 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-29 14:40:39 +0000