summaryrefslogtreecommitdiffstats
path: root/ui
Commit message (Collapse)AuthorAgeFilesLines
...
* Make inttypes.h and similar macro usage C++11-friendly.thakis@chromium.org2013-07-252-5/+5
| | | | | | | | | | | | | | | | "foo"PRIuS is a user-defined literal in C++11. Add spaces around these macros. Likewise, L"\xab"L"c" is a user-defined literal, so insert a space in the middle. No functionality change. BUG=chromium:263960 TBR=alokp@chromium.org, dmichael@chromium.org, enne@chromium.org, isherman@chromium.org, rsleevi@chromium.org, thestig@chromium.org Review URL: https://codereview.chromium.org/20182002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213566 0039d316-1c4b-4281-b951-d872f2087c98
* Move keycodes to ui namespacesgurun@chromium.org2013-07-241-2/+2
| | | | | | | | | | | | | | | | | | | | | | Move keycodes to ui namespace (anonymous namespace under ui namespace) to prevent conflicts when building android webview. Fix failure detected in Android AOSP bot http://build.chromium.org/p/chromium.fyi/builders/Android%20AOSP%20Builder%20(dbg) build log http://build.chromium.org/p/chromium.fyi/builders/Android%20AOSP%20Builder%20%28dbg%29/builds/2866/steps/compile/logs/stdio verified webview via local build. NOTRY=true TBR=ben@chromium.org BUG= Review URL: https://chromiumcodereview.appspot.com/20131002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213540 0039d316-1c4b-4281-b951-d872f2087c98
* The new alternate shelf requests that all tray / message bubbles / ↵skuhne@chromium.org2013-07-247-15/+76
| | | | | | | | | | | | | application launcher will be flush with the shelf There is one edge case left for a rotated shelf: Messages are slightly offsetted from the system menu (if existent). Beside that everything seems to work now as expected. BUG=259029 TEST=visual with L/R languages and with different shelf alignments Review URL: https://chromiumcodereview.appspot.com/19771021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213500 0039d316-1c4b-4281-b951-d872f2087c98
* Provide Android implementation of WebInputEventFactory in contentjdduke@chromium.org2013-07-244-0/+326
| | | | | | | | | | | Remove Android dependencies on WebInputEventFactory and WebKeyboardEvent implementations from content/, adding substitute methods where appropriate. BUG=263189 Review URL: https://chromiumcodereview.appspot.com/20013002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213474 0039d316-1c4b-4281-b951-d872f2087c98
* Fixes vertical alignment of RenderTextWin.yukishiino@chromium.org2013-07-241-6/+9
| | | | | | | | | | | | | I don't see the same issue of crbug.com/244323 on Windows so far, but theoretically this CL fixes the same possible issue on Windows. By the way, this CL is effective for the case that some of fonts are unexpectedly smaller than the default font. Not effective for the case that some of fonts are unexpectedly larger than the default font. So, this CL doesn't fix crbug.com/146236 . BUG=244323 TEST=none Review URL: https://chromiumcodereview.appspot.com/19734003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213383 0039d316-1c4b-4281-b951-d872f2087c98
* Make dragging outside the app list scroll back to its original position.koz@chromium.org2013-07-242-14/+41
| | | | | | | | | | | | | | | | | | | Currently when dragging an app from the app list outside the bounds of the app launcher the apps in the launcher continue to re-arrange themselves even though the cursor may be nowhere near the app launcher, which looks weird. This change makes it so that the app launcher animates back to its original state while the cursor is outside the launcher, and will cause drops to outside the app launcher to return the dragged app to its original position, which is consistent with flows such as dragging apps to the taskbar on Windows / ChromeOS. BUG=261452 Review URL: https://chromiumcodereview.appspot.com/19382003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213339 0039d316-1c4b-4281-b951-d872f2087c98
* message-center: Fix fling scroll in the list.sadrul@chromium.org2013-07-241-1/+1
| | | | | | | | | BUG=263627 R=mukai@chromium.org Review URL: https://codereview.chromium.org/19471016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213335 0039d316-1c4b-4281-b951-d872f2087c98
* Dispatch Mouse enter/exit window events (Linux Aura)sidharthms@chromium.org2013-07-241-0/+6
| | | | | | | | | | EnterNotify and LeaveNotify events will be dispatched to event handlers. BUG=263220 Review URL: https://chromiumcodereview.appspot.com/19664007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213308 0039d316-1c4b-4281-b951-d872f2087c98
* Support creating progress bar notification for Windowsjianli@chromium.org2013-07-246-12/+80
| | | | | | | | | | | | | This is the 1st patch to add progress bar notification support. It contains: 1) A new progress type is added and a new optional progress value is added. 2) NotificationView creates and adds a NotificationProgressbar child view. BUG=170924 TEST=manual test by creating a progress bar notification Review URL: https://chromiumcodereview.appspot.com/18662006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213287 0039d316-1c4b-4281-b951-d872f2087c98
* Correctly integrate StoragePartition into TestingProfile.ajwong@chromium.org2013-07-232-11/+3
| | | | | | | | | | | | | | | | | | | | | | | Until this CL, TestingProfile had 3 distinct URLRequestContexts it would return to the user: one via profile->GetDefaultStoragePartition()->GetRequestContext(), one via profile->GetRequestContext(), and one via profile->GetResourceContext->GetRequestContext(). All of these had different cookie stores. This CL unified them so they all return the one from profile->GetDefaultStoragePartition()->GetRequestContext(). This correctly mimics how production code works. Doing this had a bunch of implications: (1) Removes TestingProfile::CreateRequestContext()/ResetRequestContext() (2) Changes MockRequestContext to share the URLRequestContext with TestingProfile. (3) TestingProfile now requires all BrowserThreads. Point (3) effectively adds TestBrowserThreadBundle into a bunch more spots. Because of that, we also have the following changes: (a) AshTestBase now has a TestBrowserThreadBundle (b) Removed a bunch of real threads from tests. (c) TemplateUrlService has reworked synchronization semantics. (d) Removed MultiThreadTestHelper. (e) Added TestingIOThread class + testing API in IOThread to mock out various IO thread tasks which enervated with the new TestBrowserThreadBundle. TBR=bauerb,brettw,isherman,joth,jyasskin,mattm,mmenke,mnissler,pkasting,rkc,rlp,satorux,tim,xians,joth BUG=159193 Review URL: https://chromiumcodereview.appspot.com/17127002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213272 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Revert 210138 "Perform glReadPixels with PBOs in the gpu, if PBO...""hubbe@chromium.org2013-07-231-0/+1
| | | | | | | | | | | | | | | | | | | | | | | Third try for getting asynchrous readpixels to work everywhere. This is identical to: https://codereview.chromium.org/16831004/, but with the following fixes: OutOfProcessPPAPITests.Graphics3D (removed a check in query_tracker.cc) GLReadbackTest.ReadPixelsWithPBO (removed, no longer a valid test) GLReadbackTest.ReadPixelsWithPBOAndQuery (now uses the correct query) And, new in this CL: Disable asynchronous readpixels on macosx prior to 10.8, as it would seem that the GL_ARB_fence extension doesn't seem to work on any driver, and there are crashes in readpixel itself on intel drivers. The original CL only disabled the async readpixels path for intel drivers. BUG=258169 Review URL: https://chromiumcodereview.appspot.com/19579008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213261 0039d316-1c4b-4281-b951-d872f2087c98
* Update the screen info if the display related property has changed when resized.oshima@chromium.org2013-07-231-3/+6
| | | | | | | | | | | | | | | | This has to be done in RWHVA::SetBounds because this is called before other observers (aura::WindowObserver, gfx::DisplayObserver) get called. Also updated TestScreen to update the display when UI scale is set. Removed screen_info_out_of_date_ as this doesn't seem to be used properly. BUG=253917 TEST=covered by test. see bug for repro step. Review URL: https://chromiumcodereview.appspot.com/19293002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213252 0039d316-1c4b-4281-b951-d872f2087c98
* Update include paths in ui for base/process changes.rsesek@chromium.org2013-07-233-3/+2
| | | | | | | | | BUG=242290 R=ben@chromium.org Review URL: https://chromiumcodereview.appspot.com/19781003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213219 0039d316-1c4b-4281-b951-d872f2087c98
* Enable and disable Synced Notification Client Servicespetewil@chromium.org2013-07-231-3/+0
| | | | | | | | | | | | | | Synced Notifications can be sent from web services. This checkin will allow us to enable and disable synced notifications from specific service sources. For example, sending services could include mail, calendar, and Google+. These notifications will be displayed to the user as Rich Notifications. We are developing a protocol to send the names, app ids, and icons for these services as a new synced data type. However, until that protocol is ready, we are hardcoding the names and icons of the services into chrome. We will remove the hardcoded names and icons once the new sync datatype is ready (hopefully during the next milestone). This change also supplies the name of our first client (Google+) and an icon to use in the synced notifications settings dialog. Due to licensing restrictions, we are checking in one icon for chromium (basically a copy of the default favicon), and another one for chrome proper (this will be a separate checkin to the chrome specific codebase). BUG=254617 Review URL: https://chromiumcodereview.appspot.com/19056002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213175 0039d316-1c4b-4281-b951-d872f2087c98
* desktop aura: Fix multiple problems with ibeams in the omnibox.erg@chromium.org2013-07-232-4/+14
| | | | | | | | | | | | | | | In linux_aura, we must set cursors through the CursorClient interface instead of on the raw RootWindowHost interface because the CursorClient actually sets the system cursor types. In windows aura, we must keep track of the current cursor. We do not and instead always claim that the current cursor is the null cursor. BUG=247180 Review URL: https://chromiumcodereview.appspot.com/19882003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213167 0039d316-1c4b-4281-b951-d872f2087c98
* Cut some more dependencies from browser to child for multiple_dll modescottmg@chromium.org2013-07-231-1/+1
| | | | | | | | | | | Removes the in-process implementations for Gpu and Utility. R=jam@chromium.org, sky@chromium.org BUG=237249 Review URL: https://codereview.chromium.org/19502003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213126 0039d316-1c4b-4281-b951-d872f2087c98
* Skip painting RenderTextWin runs outside the display rect.msw@chromium.org2013-07-232-1/+7
| | | | | | | | | | | | | This should yield a minor painting performance improvement. I tested that this skips painting the expected runs locally. BUG=131660,256908 TEST=No missing/invisible text regressions, minor perf improvement for excessively long textfields text. R=asvitkine@chromium.org,ckocagil@chromium.org Review URL: https://chromiumcodereview.appspot.com/19684007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213121 0039d316-1c4b-4281-b951-d872f2087c98
* Require 100ms before re-opening a Views Combobox menu.msw@chromium.org2013-07-234-7/+20
| | | | | | | | | | | | | | | | | Views Comboboxes should close when clicked while open. (this matches MenuButton and Native Win Comboboxes) Use a timer to require 100ms before re-opening the menu. (required because of menu nested message loop complexity) Share MenuButton's kMinimumTimeBetweenButtonClicks const. BUG=260146,175843 TEST=Clicking the combobox view while its menu is open causes the menu to close without re-opening. The menu will re-open after 100ms (about as fast as you can click it again). This behavior matches other Chrome menus like the hotdog menu, bookmark menus, etc. No other behavior changes. R=sky@chromium.org Review URL: https://chromiumcodereview.appspot.com/19520020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213120 0039d316-1c4b-4281-b951-d872f2087c98
* Make 'Submit' button blue for payments dialog.estade@chromium.org2013-07-234-2/+19
| | | | | | | | | | | This also does some rewiring under the hood so that the 'Continue' button at the end of autocheckout is actually an OK button and not a CANCEL button (this should not lead to any user-visible change). BUG=261669 R=ahutter@chromium.org, msw@chromium.org, sky@chromium.org Review URL: https://codereview.chromium.org/19705008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213017 0039d316-1c4b-4281-b951-d872f2087c98
* Remove ActionBox and related code.rfevang@chromium.org2013-07-237-3/+0
| | | | | | | | | | | | ActionBox is no more, and is unlikely to be coming back. This CL removes old ActionBox code, associated resources, feature switch and extension API. BUG=234737 Review URL: https://chromiumcodereview.appspot.com/19695004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213009 0039d316-1c4b-4281-b951-d872f2087c98
* Updating XTBs based on .GRDs from branch 1547kerz@chromium.org2013-07-2295-245/+756
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212979 0039d316-1c4b-4281-b951-d872f2087c98
* linux_aura: Fix clang build and component builds.erg@chromium.org2013-07-221-1/+2
| | | | | | | | | | | | | | clang requires explicitly declared virtual destructors (to ensure they're only compiled in one translation unit), while the component build requires explicit exporting of symbols used from other shared objects. BUG=258651 TBR=sidharthms@chromium.org, sky@chromium.org Review URL: https://codereview.chromium.org/19859006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212959 0039d316-1c4b-4281-b951-d872f2087c98
* Fix border and tiling issues when rendering aura progress bars.zturner@chromium.org2013-07-221-13/+50
| | | | | | | | | | | | | | | | | | | There are 2 problems addressed by this CL. The first is that the borders were not being drawn at all because when adjusting their width for the scale factor required by the source -> dest mapping it was less than 1 and being truncated to 0. The second issue is that since we draw a separator in the progress bar, the width of each "section" may not be evenly divisible by the width of the progress bar, and the last section would be cut off. The fix here is to draw a subset of the sections with a width of 1 pixel less so that it fits exactly into the progress bar. BUG=176221 Review URL: https://chromiumcodereview.appspot.com/19682002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212955 0039d316-1c4b-4281-b951-d872f2087c98
* Add assets for disabled blue button.estade@chromium.org2013-07-2220-2/+12
| | | | | | | | | BUG=262210 R=msw@chromium.org, oshima@chromium.org, sky@chromium.org Review URL: https://codereview.chromium.org/19877002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212951 0039d316-1c4b-4281-b951-d872f2087c98
* Refactored ozone event handling for hotplug and embedder flexibiity.rjkroege@chromium.org2013-07-2212-48/+142
| | | | | | | | | | | | | This CL restructures ozone event handling logic as a prelude to supporting hotplugging on evdev and to permit external embedders to register their own EventConverterOzone instances as necessary. BUG=178543 R=sky@chromium.org Review URL: https://codereview.chromium.org/19589003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212944 0039d316-1c4b-4281-b951-d872f2087c98
* Fixed CHECK failure in ozone=1 unittests.rjkroege@chromium.org2013-07-224-0/+49
| | | | | | | | | | | | | | A change in window creation logic to resolve a TODO in RootWindowHostOzone broke multiple ozone=1 unit tests because of the absence of a SurfaceFactoryOzone implementation. This CL adds the creation of an appropriate stub SurfaceFactoryOzone to the aura test helper code. BUG=262277 R=ben@chromium.org Review URL: https://codereview.chromium.org/19482017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212907 0039d316-1c4b-4281-b951-d872f2087c98
* Add dubroy@ to WebUI OWNERS files.dubroy@chromium.org2013-07-221-0/+1
| | | | | | | | BUG=None Review URL: https://chromiumcodereview.appspot.com/19934002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212870 0039d316-1c4b-4281-b951-d872f2087c98
* Make AppListItemView's progress bar not reset to 0 while installing app.koz@chromium.org2013-07-221-0/+5
| | | | | | | | BUG=257961 Review URL: https://chromiumcodereview.appspot.com/19705012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212843 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 212778 "Colors shouldn't break runs and should be handled..."akalin@chromium.org2013-07-223-56/+22
| | | | | | | | | | | | | | | | > Colors shouldn't break runs and should be handled while drawing the text > > BUG=262119,256908 > TEST=In a views textfield, selecting half of a ligature shouldn't break the ligature. See http://www.catch22.net/tuts/uniscribe-mysteries in Firefox to see a example of how it used to look versus how it is supposed to look. > TBR=asvitkine@chromium.org > > Review URL: https://chromiumcodereview.appspot.com/19672006 TBR=ckocagil@chromium.org Review URL: https://codereview.chromium.org/19861004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212830 0039d316-1c4b-4281-b951-d872f2087c98
* Introduces the const version of GetInputMethod().yukishiino@chromium.org2013-07-204-7/+26
| | | | | | | | | | | There are cases that we need the status of the input method, but no need to change it. This CL introduces {View,Widget}::GetInputMethod() const. TEST=none Review URL: https://chromiumcodereview.appspot.com/18238018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212798 0039d316-1c4b-4281-b951-d872f2087c98
* Fixes vertical alignment of RenderText.yukishiino@chromium.org2013-07-205-13/+89
| | | | | | | | | | | | | | | (was: Issue 18848002: Shows Japanese and English mixed queries correctly.) The CL 18848002 was reverted because the new unit test, which I added, depended on the specific fonts and didn't run well on some of platforms. I've carefully chosen another font for the unit test, which is available on all platforms. BUG=244323 TEST=Test manually. Review URL: https://chromiumcodereview.appspot.com/19352002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212792 0039d316-1c4b-4281-b951-d872f2087c98
* Colors shouldn't break runs and should be handled while drawing the textckocagil@chromium.org2013-07-203-22/+56
| | | | | | | | | | BUG=262119,256908 TEST=In a views textfield, selecting half of a ligature shouldn't break the ligature. See http://www.catch22.net/tuts/uniscribe-mysteries in Firefox to see a example of how it used to look versus how it is supposed to look. TBR=asvitkine@chromium.org Review URL: https://chromiumcodereview.appspot.com/19672006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212778 0039d316-1c4b-4281-b951-d872f2087c98
* Allow noise TouchBegin to be droppedmiletus@chromium.org2013-07-201-4/+6
| | | | | | | | | | | | | | | | We currently don't detect & drop noise TouchBegin, but only for noise TouchUpdate & TouchEnd. This could result in a noise TouchBegin is translated to be a TouchPress at (0,0) and if not cancelled quickly enough, it triggers long press effect at (0,0). This CL changes to drop the noise TouchBegin. BUG=237899 TEST=2F Swipe in horizontally from side bezel, and check that no long press effect appears at (0,0) Review URL: https://chromiumcodereview.appspot.com/19649005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212736 0039d316-1c4b-4281-b951-d872f2087c98
* Introduce kb-shift-keybshe@chromium.org2013-07-208-37/+130
| | | | | | | | | | | | This CL instroduce kb-shift-key. It is extended from kb-key with the ability to listen to double click event. BUG=252751 Review URL: https://chromiumcodereview.appspot.com/19771007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212723 0039d316-1c4b-4281-b951-d872f2087c98
* views: Fix menu/combobox dropdown auto-scrollingestade@chromium.org2013-07-192-9/+13
| | | | | | | | | | | | | | | | | | | | | | | | this fixes the regression caused by r209598, and improves some menu behaviors. Before r209598: 1. starting to type a menu item would not scroll the menu if the item were off the edge 2. pressing the down arrow would move the selection down, but scroll the entire menu contents up (if scrollbars were visible). After r209598: 1. fixed 2. same 3. regression: mousing over an item would cause the menu to scroll, placing a new item under the cursor, which would cause the menu to scroll, which would place a new item under the cursor, etc. until the end of the menu was reached After this patch: 1. fixed 2. pressing the down arrow moves the selection down, but only scrolls the menu just enough such that item is visible (matches behavior of <select>s in renderer) 3. fixed. Bonus: mousing over a partially visible menu item will scroll the menu till that item is visible. BUG=258182 Review URL: https://chromiumcodereview.appspot.com/19695003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212638 0039d316-1c4b-4281-b951-d872f2087c98
* Add interrobang key to altkeys.stevet@chromium.org2013-07-191-0/+1
| | | | | | Review URL: https://chromiumcodereview.appspot.com/19772010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212560 0039d316-1c4b-4281-b951-d872f2087c98
* Add Level5Shift key support into KeyboardCodeConversion.nona@chromium.org2013-07-191-0/+4
| | | | | | | | | | | Without this conversion, key is rejected. BUG=None TEST=Manually confirmed the key is sent to web page. Review URL: https://chromiumcodereview.appspot.com/19194003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212542 0039d316-1c4b-4281-b951-d872f2087c98
* The previous implementation is not correct, it depended on the Fullscreen ↵michaelbai@chromium.org2013-07-191-0/+10
| | | | | | | | | | | | | | video class, but the PowerSaveBlocker could be used for embedding video or the use case which isn't related to the video at all. This patch adds new API to PowerSaveBlocker. BUG=247892 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=212022 Review URL: https://chromiumcodereview.appspot.com/17175009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212536 0039d316-1c4b-4281-b951-d872f2087c98
* requestAutocomplete: fix some text colorsestade@chromium.org2013-07-182-7/+21
| | | | | | | | | | most notably, make the legal documents text readable. BUG=260355 Review URL: https://chromiumcodereview.appspot.com/19531006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212477 0039d316-1c4b-4281-b951-d872f2087c98
* App Indicator implementationsidharthms@chromium.org2013-07-184-0/+75
| | | | | | | | | | | | | | | | | | | | | | | | App Indicator has been implemented as part of libgtk2ui (since app indicators use gtk). A StatusIconLinux interface has been created alongside linux_ui interface since we don't want gtk2ui library to depend on the "browser" target (where status_icon.h is). This interface will be used by implementions of linux_ui (e.g. libgtk2ui) to support status icons. AppIndicatorIcon is such an implementation (part of libgtk2ui) which enables app indicator support. App indicators require us to pass in a GtkMenu (they will not be shown without a menu) and so some "tools" have been added to create a GtkMenu from a menu model (similar to GtkMenu implementation). App indicators do not support setting the icon from a pixbuf and so we have to create a temporary icon file and pass in the icon directory to libappindicator. Note: This does not support updating the app indicator menus automatically when the menu-model is changed externally (i.e. if the change is not due to a menu item click). BUG=258651 Review URL: https://chromiumcodereview.appspot.com/18334003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212476 0039d316-1c4b-4281-b951-d872f2087c98
* Ozone API changes for third-party implementationstiago.vignatti@intel.com2013-07-183-7/+24
| | | | | | | | | | Initialize RootWindowHostOzone with native AcceleratedWidget BUG= Review URL: https://chromiumcodereview.appspot.com/19662002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212475 0039d316-1c4b-4281-b951-d872f2087c98
* Observes work area change and auto-hide for notifications.mukai@chromium.org2013-07-183-10/+18
| | | | | | | | | BUG=249509 R=dewittj@chromium.org Review URL: https://chromiumcodereview.appspot.com/19291004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212431 0039d316-1c4b-4281-b951-d872f2087c98
* In immersive mode when top container is closed, decrease the hit target of ↵wnwen@chromium.org2013-07-181-0/+4
| | | | | | | | | | | | | | | | | | | | | | the render view. This steals a few pixels from the content so that slide gestures can be appropriately generated even if the content page consumes touch events (in which case without stealing these pixels result in no gestures being generated and so no sliding out of the top container in immersive mode). Increased number of pixels to steal slightly (from 5 to 8) to improve accuracy, may be tweaked later. BUG=chromium:252225 TEST=Works reliably even when page consumes touch/mouse events. Works on rotation. TBR=ben@chromium.org Review URL: https://chromiumcodereview.appspot.com/18539015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212428 0039d316-1c4b-4281-b951-d872f2087c98
* Cleaned up includes in SurfaceFactoryOzone.ccrjkroege@chromium.org2013-07-181-2/+1
| | | | | | | | | BUG=none R=sky@chromium.org Review URL: https://codereview.chromium.org/19235012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212416 0039d316-1c4b-4281-b951-d872f2087c98
* reland of http://crrev.com/212230 Create top-level separate targets for...scottmg@chromium.org2013-07-182-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Original CL here: https://codereview.chromium.org/17619005/ Changed since previous landing is diff between ps1 and ps2. Diff since previous landing is a bit noisy, but in those files against original is relatively small. The conditions for the defines were incorrect and are simpler (and correct) now. Previously: Create top-level separate targets for browser and child dlls The general idea is that there's top level targets chrome and chrome_child, and corresponding content_app and content_app_child that depend on only the subtargets that should be included in the appropriate dll. Currently (probably) Windows-only and requires setting chrome_multiple_dll=1 for gyp. Links, but Blink is still included in browser. Single-process mode is currently disabled when chrome_multiple_dll is set. Current graph is at: http://commondatastorage.googleapis.com/chromelinkgraph/deps.html generated by "python tools\win\split_link\graph_dependencies.py deps.html" Remove the previous hacky-er attempt at this that was named "split dll". TBR=jam@chromium.org BUG=237249, 256965 Review URL: https://codereview.chromium.org/19572013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212415 0039d316-1c4b-4281-b951-d872f2087c98
* Remove --enable-d3d11 switch.apatrick@chromium.org2013-07-183-7/+1
| | | | | | | | It's interfering with our stability stats. Review URL: https://chromiumcodereview.appspot.com/19671003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212402 0039d316-1c4b-4281-b951-d872f2087c98
* Fix drawing the inactive tab background when using --use-core-animationpkotwicz@chromium.org2013-07-181-1/+3
| | | | | | | | | | | BUG=260139 TEST=Manual, see bug R=ccameron1 TBR=sail Review URL: https://chromiumcodereview.appspot.com/18968003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212388 0039d316-1c4b-4281-b951-d872f2087c98
* Replace third_party/icu/public with third_party/icu/source in the include ↵jshin@chromium.org2013-07-189-13/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | directives. This is to move back icu headers in third_party/icu/public/{i18n,common}/unicode back to their upstream locations in third_party/icu/source/{i18n,common}/unicode. http://codereview.chromium.org/18836004 has is a CL to move ICU header files. Roll ICU to the version with the above ICU CL (http://crrev.com/211851 ). In addition to the global replacement of third_party/icu/public with third_party/icu/source, the top-level DEPS, DEPS in printing and chrome/ are tightened up. (the latter two were too permissive (it used to allow any header from third_party/icu). Besides, sync '-foo' list in ios/public/DEPS with '+foo' in the top-level DEPS and build/linux/unbundled/icu.gyp is updated. BUG=251433 TEST=Compile succeeds on all bots. checkdeps.py does not find any error. TBR=brettw,sky,wtc Review URL: https://chromiumcodereview.appspot.com/18252003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212324 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 212008 "cc: Remove TextureLayer::SetTextureId and Texture..."aberent@google.com2013-07-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | Temporary revert of this as Android Build Sheriff until the Android UI stops using SetTextureId. Needed since it is currently impossible to roll the version of chromium used by Android past this change. > cc: Remove TextureLayer::SetTextureId and TextureLayer::WillModifyTexture > > These are not used anymore except for clearing the client-provided texture, so > this removes 1 of 4 TextureLayer paths, and implifies externally-exposed state. > > BUG=None > > Review URL: https://chromiumcodereview.appspot.com/19303003 BUG=261151 TBR=piman@chromium.org Review URL: https://codereview.chromium.org/19463010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212321 0039d316-1c4b-4281-b951-d872f2087c98
* Fix problem with touch selection handles when flickedmohsen@chromium.org2013-07-181-0/+1
| | | | | | | | | | | After flicking a touch selection handle, moving the mouse or typing with keyboard should hide the handles. But, this was not the case. BUG=261213 Review URL: https://chromiumcodereview.appspot.com/19582004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212299 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-16 17:12:56 +0000