summaryrefslogtreecommitdiffstats
path: root/remoting
Commit message (Collapse)AuthorAgeFilesLines
* Fix installer download for apps v2.jamiewalch@chromium.org2014-05-152-3/+8
| | | | | | | | | | | | | | | | | This is a poor-man's solution to unblock the apps v2 release. It causes an existing Chrome window (or a new one if there aren't any) to download the installer. This is needed because the v2 app doesn't have a brower context, which means no download shelf for the user to click when the download completes. The UX is pretty horrible because the Chrome window pops on top of the app window, typically obscuring the instructions. I'm open to better solutions. This also fixes a bug in the host setup and install dialogs, which were not showing the translucent screen that normally obscures the main UI while a modal dialog is open. Review URL: https://codereview.chromium.org/282113002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@270802 0039d316-1c4b-4281-b951-d872f2087c98
* Android: cleans up jni_generator_ptr_type.bulach@chromium.org2014-05-151-1/+0
| | | | | | | | | | | | | The underlying rule is now "long" by default. Mechanical change: git grep -l jni_generator_ptr_type | xargs sed -i /jni_generator_ptr_type/d BUG=317523 TBR=darin@chromium.org Review URL: https://codereview.chromium.org/288963002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@270750 0039d316-1c4b-4281-b951-d872f2087c98
* Implement apps v2 custom window frame.jamiewalch@chromium.org2014-05-1421-81/+533
| | | | | | | | | | | | | | | | | The default apps v2 container is pretty basic. We want to provide something that looks prettier and also implements some functionality specific to our use-case: * When connected to a host, a disconnect icon is added to the window controls (it's therefore no longer needed in the tool-bar). * When connected to a host, maximize == full-screen. * In full-screen mode, the window controls are still accessible, but are auto-hidden near the top-left corner (but not obscuring it, since it's often a hot-spot on the server). * For touch-screen devices with no concept of hover, clicking the "stub" will also reveal the controls. There should be no change to the v1 UX, but I don't plan on landing this CL before the M36 branch point, just in case. BUG=134213 Review URL: https://codereview.chromium.org/265393005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@270342 0039d316-1c4b-4281-b951-d872f2087c98
* Cancel PIN browser testkelvinp@chromium.org2014-05-147-40/+357
| | | | | | | | | Update PIN browser test Invalid PIN browser test Review URL: https://codereview.chromium.org/273753002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@270317 0039d316-1c4b-4281-b951-d872f2087c98
* Chromoting iOS clientdcaiafa@chromium.org2014-05-1375-0/+9289
| | | | | | | | | | | | | | | | | | | This is a sub-set of: https://codereview.chromium.org/186733007/ It doesn't include the .xcodeproj files which were causing problems with "git cl" due to being in the root .gitignore. They won't be necessary after gyp integration. This is just a code drop. Nothing is being built at the moment. NOTRY=true TBR=sergeyu@chromium.org BUG=331356 Review URL: https://codereview.chromium.org/278863003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@270143 0039d316-1c4b-4281-b951-d872f2087c98
* Fix lint issues with Chromoting for Android.sungmann.cho@navercorp.com2014-05-132-8/+15
| | | | | | | | | | | | | | | | Currently, the lint warns at: Error: Field requires API level 18 (current min is 14): android.provider.Settings#EXTRA_ACCOUNT_TYPES [InlinedApi] Error: Field requires API level 16 (current min is 14): android.view.View#SYSTEM_UI_FLAG_FULLSCREEN [InlinedApi] So we need to add @TargetApi to suppress these lint error. BUG=327768 Review URL: https://codereview.chromium.org/273313003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@269995 0039d316-1c4b-4281-b951-d872f2087c98
* Implement VP9/I444 encode support in the Chromoting host.wez@chromium.org2014-05-128-121/+160
| | | | | | | | | | This will be selectable by clients that want to avoid I420 artefacts. BUG=260879,134202 Review URL: https://codereview.chromium.org/261753013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@269774 0039d316-1c4b-4281-b951-d872f2087c98
* Use sane default screen size if RANDR not supportedlambroslambrou@chromium.org2014-05-101-12/+32
| | | | | | | | | | | | | In order of precedence, set size according to: * Command line parameters if present * Environment variable if present * 1600x1200,3840x1600 if RANDR is present, otherwise just 1600x1200. R=jamiewalch@chromium.org Review URL: https://codereview.chromium.org/278753002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@269476 0039d316-1c4b-4281-b951-d872f2087c98
* Initialize ICU on remoting_native_messaging_hostdcaiafa@google.com2014-05-091-0/+4
| | | | | | | | | BUG=371432 R=rmsousa@chromium.org Review URL: https://codereview.chromium.org/274933002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@269413 0039d316-1c4b-4281-b951-d872f2087c98
* Fix psutil usage in Chromoting Linux Me2Me script.lambroslambrou@chromium.org2014-05-091-8/+6
| | | | | | | | | | | | | | | | | | This code was failing in Ubuntu Trusty because psutil is at version 1.2.1, but the previous code was incorrectly detecting it as a "new" 2.0+ API. Fixed the check to be more explicit. Also, this bypasses the issue of psutil.Error not being defined in older versions by explicitly trapping the individual exception types instead of psutil.Error. Note that psutil.error was always a private API and should never have been used in the first place. TEST=Works in Ubuntu Precise and Trusty R=jamiewalch@chromium.org Review URL: https://codereview.chromium.org/272543006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@269407 0039d316-1c4b-4281-b951-d872f2087c98
* Implement stats reporting in Android clientlambroslambrou@chromium.org2014-05-098-1/+639
| | | | | | | | | | | | | | | | | | | This reports the same connection statistics and session change events that are currently reported by the web-app. Caveats: This does not provide Chrome or Webapp versions - instead it reports the Android OS version, and the app version, under differently-named keys. Session termination events don't seem to be reported. This is a limitation of the Android client that might not be easy to work around. BUG=368015 R=rmsousa@chromium.org Review URL: https://codereview.chromium.org/270613005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@269404 0039d316-1c4b-4281-b951-d872f2087c98
* Update Play Store what's-new text for Chromoting app.lambroslambrou@chromium.org2014-05-091-1/+2
| | | | | | | | R=jamiewalch@chromium.org Review URL: https://codereview.chromium.org/275703002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@269377 0039d316-1c4b-4281-b951-d872f2087c98
* Refactor HostSetupDialog and HostInstallDialog.weitaosu@chromium.org2014-05-096-83/+126
| | | | | | | | | | | | | | | 1. Moved all the host installation logic to the HOST_INSTALL step in HostSetupDialog 2. On Windows host installation now occurs before the pin prompt when user enables remote connection. 3. HostInstallDialog now handles both the prompt (Linux/Mac) and non-prompt (windows) scenarios. 4. Renamed onDone and onError in HostInstallDialog to onOk and onCancel. The install prompt doesn't perform any task itself and won't incur any error so onOk an onCancel are better names. This CL is a precursor to the change that enables automatic host installation for IT2Me on windows. BUG=134215 Review URL: https://codereview.chromium.org/243993002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@269344 0039d316-1c4b-4281-b951-d872f2087c98
* This change provides a basic infrastructure for writing browser test in ↵kelvinp@chromium.org2014-05-096-2/+207
| | | | | | | | | | | | | | | | | | | | | | | JavaScript, which has several advantages. 1. The JavaScript lives in a separate file instead of inline strings in the C++, which is much more readable. Since it is not part of the browserTest executable, you can modify it on the fly without re-linking (which takes 70s on a Engineering desktop), that makes development faster. 2. Instead of using sleeps to determine whether an action has happened, we can hook specific events in JavaScript. This allow more reliable tests that run in a more timely manner. Overview: - The infrastructure lives in two file: browserTest.js provides basically functionality for reporting results back to the C++ layer remote_desktop_browserTest provides basic functionality for loading/injecting JavaScript and executing the tests. - To define a browserTest, create a class under the browserTest namespace with a run method. browserTest.Foo_Test = function () {} browserTest.Foo_Test.prototype.run = function () { ... } - You can then call the following from C++ RunJavaScriptTest(web_content, "Foo_Test", "{ field1: 'data'}" Review URL: https://codereview.chromium.org/268813006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@269173 0039d316-1c4b-4281-b951-d872f2087c98
* Clean up common parts of VPX codec initialization.wez@chromium.org2014-05-092-34/+41
| | | | | | | | | | | This includes some improvements & fixes: - VP9 is now initialized for multi-threaded encode. - Frame timestamp base is correctly set to milliseconds. - Frame timestamps are now set based on elapsed time. Review URL: https://codereview.chromium.org/265113002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@269151 0039d316-1c4b-4281-b951-d872f2087c98
* Don't use talk_base::CreateRandomString() to generate ICE credentials.sergeyu@chromium.org2014-05-091-4/+21
| | | | | | | | | | | | | | talk_base::CreateRandomString() uses NSS internally, calling PK11_GenerateRandom() and that sometimes fails. With this change remoting will use base::RandBytesAsString() to generate ICE credentials. This is mostly a workaround until we figure out why talk_base::CreateRandomString() fails. BUG=364689 Review URL: https://codereview.chromium.org/272543002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@269126 0039d316-1c4b-4281-b951-d872f2087c98
* Better icon for hiding the action-bar in Chromoting Android client.lambroslambrou@chromium.org2014-05-097-5/+6
| | | | | | | | | | | | This changes the icon, and fixes the hover text to say "Full screen" instead of "Close". BUG=371461 R=jamiewalch@chromium.org Review URL: https://codereview.chromium.org/271823008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@269121 0039d316-1c4b-4281-b951-d872f2087c98
* Remove {linux|android}_use_tcmalloc and switch to use_allocator in Chromium.dmikurube@chromium.org2014-05-073-10/+5
| | | | | | | | | | | | | | If this change breaks some bots, please try restarting the bot before reverting it. http://crrev.com/264460 may not be effective yet until restarting. See the bug and http://crrev.com/255129 for the details. BUG=345554 Review URL: https://codereview.chromium.org/258433005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@268876 0039d316-1c4b-4281-b951-d872f2087c98
* Remove dead code in ConnectionToHostsergeyu@chromium.org2014-05-072-7/+0
| | | | | | | | TBR=jamiewalch@chromium.org Review URL: https://codereview.chromium.org/269313005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@268843 0039d316-1c4b-4281-b951-d872f2087c98
* Move IsStringUTF8/ASCII to base namespacebrettw@chromium.org2014-05-071-1/+1
| | | | | | | | TBR=sky@chromium.org Review URL: https://codereview.chromium.org/270183002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@268754 0039d316-1c4b-4281-b951-d872f2087c98
* Updating XTBs based on .GRDs from branch 1916karen@chromium.org2014-05-0641-44/+1356
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@268604 0039d316-1c4b-4281-b951-d872f2087c98
* Add support for arm64dati91@gmail.com2014-05-061-0/+4
| | | | | | | | | | | | Add arm64 target to GYP files. This is for getting a build of content shell for ARM64. BUG=354405 R=garykac@chromium.org Review URL: https://codereview.chromium.org/243163002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@268447 0039d316-1c4b-4281-b951-d872f2087c98
* Don't send mouse events if the plugin doesn't have focus.jamiewalch@chromium.org2014-05-062-1/+14
| | | | | | | | | | This works around http://crbug.com/246335 and reinstates the fix for http://crbug.com/236549. BUG=236549 Review URL: https://codereview.chromium.org/136093013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@268435 0039d316-1c4b-4281-b951-d872f2087c98
* Ensure that Y, U and V planes have 16-byte alignment & stride.wez@chromium.org2014-05-031-26/+23
| | | | | | | | | This ensures that we're able to use the fast path during colour conversion operations. Review URL: https://codereview.chromium.org/265103002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@268063 0039d316-1c4b-4281-b951-d872f2087c98
* Fix <video> positioning for the MediaSource-based renderingsergeyu@chromium.org2014-05-032-4/+11
| | | | | | | | | | | | | <video> must always be placed under the plugin, but it wasn't always positioned properly. Moved video-container inside horizontally-centered div so now video-container always occupies the same area as the <video> and the plugin. BUG=321825 Review URL: https://codereview.chromium.org/269793002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@268005 0039d316-1c4b-4281-b951-d872f2087c98
* Add dcaiafa@chromium.org to remoting/OWNERSdcaiafa@chromium.org2014-05-021-0/+1
| | | | | | | | R=wez@chromium.org Review URL: https://codereview.chromium.org/261133002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267841 0039d316-1c4b-4281-b951-d872f2087c98
* Fix MediaSourceVideoRenderer to generate "live stream"sergeyu@chromium.org2014-05-022-2/+20
| | | | | | | | | | | | | | | | | | In order for MediaStream to be rendered with 0 delay the stream must be marked as "live". Chrome detects liveness of a stream by presense of DateUTC and also unknown stream duration and size (see crrev.com/266452). Now the renderer properly sets DateUTC element in the stream it generates. Also changed the renderer to add DefaultDuration, which specifies default frame duration. Without it the stream parser has to delay the stream by one frame in order to calculate duration of each frame. BUG=321825 Review URL: https://codereview.chromium.org/266733002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267807 0039d316-1c4b-4281-b951-d872f2087c98
* Fix MonitoredVideoStubTest failure in memory runskelvinp@chromium.org2014-05-021-1/+9
| | | | | | | | | | | | | | Cause: The test fails because on slow machines, the connectivity check timer may fires before the test finishes. As a result, there is an unexpected transition to not ready on the video channel. Fix: Take that transition into account. BUG=369191 Review URL: https://codereview.chromium.org/264963007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267773 0039d316-1c4b-4281-b951-d872f2087c98
* Remove PlatformFile from remoting native messaging.rvargas@chromium.org2014-05-0215-137/+118
| | | | | | | | BUG=322664 Review URL: https://codereview.chromium.org/254863002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267737 0039d316-1c4b-4281-b951-d872f2087c98
* Remove JNIEnv::NewStringUTF calls. Use ConvertUTF8ToJavaString instead.sungmann.cho@navercorp.com2014-05-021-5/+8
| | | | | | | | BUG=290232 Review URL: https://codereview.chromium.org/262803006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267684 0039d316-1c4b-4281-b951-d872f2087c98
* Smart Reconnect kelvinp@chromium.org2014-05-016-45/+239
| | | | | | | | | | | | | | | | | | | | | This CL serves to make the experience below better “I typically have to manually reconnect 20-40 times per day when working remotely, about 10 reconnects are due to wifi zone changes, and 20 are due to closing my laptop screen (Chromebook Pixel). “ - A customer Cause: There are three factors that causes the connection to drop 1. When the client is suspended, the host times out in 1 min. This is particular common when the user closes the lid of the laptop and walk to another room for meeting. (P1) 2. When the client is not suspended, but cannot reach the host (network changes, host_is_offline) a. If the timeout is less than 1 min, it will try to reconnect, however, the reconnect could takes up to 2 min. Most people won't have that kind of patience to wait for the reconnect. (P2) b. If the timeout is larger than 1 min, it will timeout. Fix: This change addresses (1) and (2b) by listening to the changes in connection state of the session. If it transits from CONNECTED to FAILED and the host is not offline, we reconnect. In order for this to work smoothly, the timeout of session initiation and session accept needs to be increased, which is included in part II. Review URL: https://codereview.chromium.org/245983003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267671 0039d316-1c4b-4281-b951-d872f2087c98
* Updating XTBs based on .GRDs from branch 1847dxie@chromium.org2014-05-0141-1353/+41
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267598 0039d316-1c4b-4281-b951-d872f2087c98
* Renamed namespaces of url lib.vitalybuka@chromium.org2014-05-011-6/+6
| | | | | | | | | | | | | url_util -> url url_parse -> url url_canon -> url BUG=364747 TBR=atwilson,battre Review URL: https://codereview.chromium.org/262593002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267579 0039d316-1c4b-4281-b951-d872f2087c98
* Smart reconnect part II - plugin and hostkelvinp@chromium.org2014-05-0112-47/+252
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This CL serves to make the experience below better “I typically have to manually reconnect 20-40 times per day when working remotely, about 10 reconnects are due to wifi zone changes, and 20 are due to closing my laptop screen (Chromebook Pixel). “ - A customer Cause: 1. The current implementation of connectivity is not very reliable. It typically takes 5 seconds for us to grey out the app when there is no network connectivity. The app feels irresponsive to network connectivity There are three factors that causes the connection to drop 2. When the client is suspended, the host times out in 1 min. This is particular common when the user closes the lid of the laptop and walk to another room for meeting. (P1) 3. When the client is not suspended, but cannot reach the host (network changes, host_is_offline) a. If the timeout is less than 1 min, it will try to reconnect, however, the reconnect could takes up to 2 min. Most people won't have that kind of patience to wait for the reconnect. (P2) b. If the timeout is larger than 1 min, it will timeout. Fix: 1. To Fix (1) In a healthy connection, the host send video frames to the client periodically. We can improve the reliability of connection detection to within 1s by checking whether we have received any frames within the last second. 2. To Fix (1) and (2b), we listens for the change in connection state of the session, if it transits from CONNECTED to FAILED and the host is not offline, we reconnect. In order for this to work smoothly, this change increases the timeout of session initiation and session accept. 3. To Fix (3a), when we detect the network connectivity is up again. We will let the transport layer to re-negotiate the transport channels. However, if it doesn't finishes its job within 5 second, the plugin to transit to FAILED state so that the webapp can reconnect 4. I have written an unittest for the video_channel_monitoring code and tested out the app on the chromebook pixel. The experience definitely feels better. BUG=264300 Review URL: https://codereview.chromium.org/243483004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267384 0039d316-1c4b-4281-b951-d872f2087c98
* Remove PPB_Ext_Socket_Dev.yzshen@chromium.org2014-04-302-0/+3
| | | | | | | | | BUG=366304,244653,312916,314899 TEST=None Review URL: https://codereview.chromium.org/252923005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267348 0039d316-1c4b-4281-b951-d872f2087c98
* Use chrome.app.window full-screen API for apps v2.jamiewalch@chromium.org2014-04-307-23/+313
| | | | | | | | | | | | | | | | | | This allows us to hook onMaximized to enter full-screen which is a cleaner UX. In the future, we will also have on-screen auto-hide close/minimize/restore controls in full-screen mode, which will eliminate the need for the tool-bar menu entry completely. See https://developer.chrome.com/apps/app_window#type-AppWindow for details of the API, and http://code.google.com/p/chromium/issues/detail?id=364942 for a discussion of why this behaviour is not going to be supported by requestFullscreen. BUG=134213,252927 NOTRY=true Review URL: https://codereview.chromium.org/252783003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267329 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 267242 "Revert 267234 "New policies: enable/disable relay..."noamsml@google.com2014-04-3014-30/+276
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reland due to accidental incorrect revert. > Revert 267234 "New policies: enable/disable relay; port range" > > > New policies: enable/disable relay; port range > > > > Add new Chromoting policies: > > > > "RemoteAccessHostAllowRelayedConnection" > > bool, default true > > It can be set to false to disable the use of relay servers if NAT > > traversal is enabled. > > > > "RemoteAccessHostUdpPortRange" > > string, default "" > > Can be used to specify a range in the form "<min-port>-<max-port>" to > > restrict the range of UDP ports available to the host for connections. > > E.g. "12400-12409" > > > > BUG=355168 > > > > Review URL: https://codereview.chromium.org/209323002 > > TBR=dcaiafa@chromium.org > BUG=368724 > > Review URL: https://codereview.chromium.org/268483003 TBR=noamsml@google.com Review URL: https://codereview.chromium.org/261633005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267248 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 267234 "New policies: enable/disable relay; port range"noamsml@google.com2014-04-3014-276/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | > New policies: enable/disable relay; port range > > Add new Chromoting policies: > > "RemoteAccessHostAllowRelayedConnection" > bool, default true > It can be set to false to disable the use of relay servers if NAT > traversal is enabled. > > "RemoteAccessHostUdpPortRange" > string, default "" > Can be used to specify a range in the form "<min-port>-<max-port>" to > restrict the range of UDP ports available to the host for connections. > E.g. "12400-12409" > > BUG=355168 > > Review URL: https://codereview.chromium.org/209323002 TBR=dcaiafa@chromium.org BUG=368724 Review URL: https://codereview.chromium.org/268483003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267242 0039d316-1c4b-4281-b951-d872f2087c98
* New policies: enable/disable relay; port rangedcaiafa@chromium.org2014-04-3014-30/+276
| | | | | | | | | | | | | | | | | | | | | Add new Chromoting policies: "RemoteAccessHostAllowRelayedConnection" bool, default true It can be set to false to disable the use of relay servers if NAT traversal is enabled. "RemoteAccessHostUdpPortRange" string, default "" Can be used to specify a range in the form "<min-port>-<max-port>" to restrict the range of UDP ports available to the host for connections. E.g. "12400-12409" BUG=355168 Review URL: https://codereview.chromium.org/209323002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267234 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 267030 "Build remoting for PNaCl"sergeyu@chromium.org2014-04-3014-407/+18
| | | | | | | | | | | | | | | > Build remoting for PNaCl > > BUG=276739 > R=jamiewalch@chromium.org > > Review URL: https://codereview.chromium.org/234023003 TBR=sergeyu@chromium.org Review URL: https://codereview.chromium.org/254243002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267064 0039d316-1c4b-4281-b951-d872f2087c98
* Build remoting for PNaClsergeyu@chromium.org2014-04-3014-18/+407
| | | | | | | | | BUG=276739 R=jamiewalch@chromium.org Review URL: https://codereview.chromium.org/234023003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267030 0039d316-1c4b-4281-b951-d872f2087c98
* Add systemwide session file for Chromotinglambroslambrou@chromium.org2014-04-281-7/+4
| | | | | | | | | | | | This adds /etc/chrome-remote-desktop-session to the list of files that the script looks for when deciding what session to start. BUG=366759 NOTRY=true Review URL: https://codereview.chromium.org/254393003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@266613 0039d316-1c4b-4281-b951-d872f2087c98
* Don't throw an exception if onfullscreenchanged fires after the plugin isjamiewalch@chromium.org2014-04-281-3/+5
| | | | | | | | | | | | | | | | removed. We explicitly cancel full screen mode on disconnection, which was resulting in an exception in the event handler, preventing the full-screen class from being removed from the <html> node. The left the plugin container full-screen on top of the Disconnected dialog, making it unclickable. BUG=365920 NOTRY=true Review URL: https://codereview.chromium.org/258863003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@266464 0039d316-1c4b-4281-b951-d872f2087c98
* A simple implementation to augment JavaScript objects with eventskelvinp@chromium.org2014-04-253-1/+233
| | | | | | | | | | | | | | | | | | | | | | | | | For example, to create an alarm event for SmokeDetector function SmokeDetector() { this.defineEvents(['alarm']); }; base.augment(SmokeDetector, base.Events); To fire an event SmokeDetector.prototype.onCarbonMonoxideDetected = function () { var param = {} // optional parameters this.raiseEvent('alarm', param); } To listen to an event var smokeDetector = new SmokeDetector(); smokeDetector.addEventListener('alarm',listenerObj.someCallback,listenerObj); The code lives in (base.js), a module that contains JavaScript utility components and methods for the web app. Review URL: https://codereview.chromium.org/245923002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@266164 0039d316-1c4b-4281-b951-d872f2087c98
* Refactor GYP targets for Android Chromoting clientlambroslambrou@chromium.org2014-04-238-81/+88
| | | | | | | | | | | | | | | | | | | | | | | | | | This creates a separate target, remoting_java, that builds the Java code and resources. The remoting_apk target depends on this target and builds the final APK. Several changes were needed, since the build/java.gypi file has some features and checks not present in build/java_apk.gypi: * switch/case statements changed to if/else chains, since the generated R.java uses 'int' instead of 'const int' for resource IDs. * XML style fixes necessitated by the lint-style checking, and v14 resource generation. * A new Java class added: RemotingApplication. This is needed right now because the APK build step requires at least one Java source file. In future, this class will override onCreate(), and a different override will be used for official builds, to dependency-inject Java code that requires closed-source dependencies (such as the Help+Feedback implementation). TEST=Builds and runs. Touching various files triggers rebuild. Review URL: https://codereview.chromium.org/245893004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@265750 0039d316-1c4b-4281-b951-d872f2087c98
* Fixed multi-monitor mouse coordinates.jamiewalch@chromium.org2014-04-191-2/+3
| | | | | | | | BUG=359334 Review URL: https://codereview.chromium.org/243943002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@264905 0039d316-1c4b-4281-b951-d872f2087c98
* Remove workaround for an old bug in WCS.sergeyu@chromium.org2014-04-192-33/+0
| | | | | | | | | | | Previously WCS would not always set correct IDs in the responses. We worked this problem around by trying to match pending request to each response, even when they have different IDs. That doesn't make sense anymore because the WCS bug was fixed long time ago. Review URL: https://codereview.chromium.org/240023006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@264899 0039d316-1c4b-4281-b951-d872f2087c98
* Use Immersive mode in Chromoting Android client on supported deviceslambroslambrou@chromium.org2014-04-181-3/+30
| | | | | | | | | | | This detects if the device is running KitKat or higher, and sets the display to Immersive fullscreen mode when the action-bar is hidden. BUG=338773 Review URL: https://codereview.chromium.org/240153008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@264738 0039d316-1c4b-4281-b951-d872f2087c98
* Ignore clip-rect in the chromoting client pluginsergeyu@chromium.org2014-04-181-6/+11
| | | | | | | | | | | | | | | In some cases Chrome passes incorrect clip-rect to the plugin, and so the plugin doesn't render content correctly in such cases. Fixed the plugin to ignore clip-rect from the browser. This may degrade performance in some cases, but not by much and only until we switch to using MediaSource API for rendering. BUG=360240 Review URL: https://codereview.chromium.org/240833008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@264727 0039d316-1c4b-4281-b951-d872f2087c98
* Remove unused input_shlib_pathcjhopman@chromium.org2014-04-171-1/+0
| | | | | | | | | | This path is now only inferred from test_suite_name. TBR=darin NOTRY=true Review URL: https://codereview.chromium.org/226353002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@264666 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-15 05:00:49 +0000