| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
bug: 18027885
Change-Id: Ie1db66432f0bd2b2eaaf2a7998828f69145645d9
|
| |
|
|
|
|
|
| |
Do not call WebView methods from a background thread.
Bug: 5090601
Change-Id: If72d86c6a68932787b14d7eb11c3a351ac1f8385
|
| |
|
|
|
|
|
|
| |
Bug: 5007226
This is sort of a "nuke it from orbit" fix to prevent the crash as
it is a test blocker. Bug 5086504 filed to track a "proper" fix
Change-Id: Ifd02a1fee05a05d61d70724a1ae758701679fc27
|
| |
|
|
|
|
| |
Bug: 5081641
Change-Id: I1c625e3528de9a7cd37dae5b8b428ff141759e14
|
| |
|
|
|
|
|
|
|
|
| |
Bug: 5007226
The delay dismissing of the dialog opened a situation where
the dialog would attempt to be dismissed after the activity was
destroyed. This just removes the cleverness (which we can revisit
later)
Change-Id: I2bde130f5ffe31f5d33db7f107c42e881fea1d45
|
| |
|
|
|
|
|
|
| |
It now seems to work pretty reliably. Nice. Requires changes to SearchBox
API in frameworks/base:
Depends on change: If283ecdfa62aecb1fa697b1a2cd43b771b908d72
Change-Id: I5af94c8df8f24dfafb02c4052381aa547c72684c
|
| |
|
|
|
|
| |
Bug: 4971133
Change-Id: I40ecdf4ff6c27d3eb9f4f55360552030b215913f
|
| |
|
|
|
|
|
|
| |
Bug: 4190594
check if dialog is still showing
before calling dismiss.
Change-Id: If8a06d762fbe1cc2ac4a00b0b4fe32f7d54380d8
|
| |
|
|
|
|
|
|
| |
Only attempt pre-login once unless the Browser's data is cleared. Remove
preferences for pre-login and code to detect cookies.
Bug: 3367381
Change-Id: I321a7c09be27ff6f3f570d0b9963ee2984b01c4a
|
| |
|
|
|
|
|
|
|
|
|
| |
Pause/resume timers is really broken. If the user exits the Browser, the process
is still around with paused timers. If pre-login needs to run, timers will be
stalled during the process. This is because there is no current tab during
onResume. Make sure to call resumeTimers and start the cookie sync manager
before handling pre-login.
Bug: 3474608
Change-Id: I12be617947f3ae54a206e31760a2973f81252f50
|
| |
|
|
|
| |
Bug: 3437220
Change-Id: Idcdd6582a9bdedd795cb9cf39ffd8ff2e22cdf22
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
If ClientLogin issues session cookies, we do not want to clear them immediately
after getting them from login. If we are not going to restore tabs, go ahead
and clear the cookies before attempting pre-login. Keep track of the tab to
restore so that we don't need to figure it out again. Requires a change in
frameworks/base that exposes the CookieManager api.
If we receive a 403 from IssueTokenAuth, inval the auth tokens and try again.
Bug: 3421214
Change-Id: I5dd4cc0eba365a20a731ac43dd2571ef6274eaa9
|
| |
|
|
|
|
|
| |
Search for ASIDAP using the /a/ path to find a hosted account.
Bug: 3396570
Change-Id: I10cbc7f337532d59e405804724e6bc0be4e669d8
|
| |
|
|
|
|
|
|
| |
Refactor GoogleAccountLogin to handle the progress dialog. Store the last login
time and login after a week to refresh cookies.
Bug: 3367395
Change-Id: I62a277610af5b642f51cc775f17806c558812d4a
|
| |
|
|
|
| |
Bug: 339657
Change-Id: I9372d22f4e7101392a24147e5db5670bfebd3835
|
| |
|
|
|
|
|
|
|
| |
If the user cancels the login event, mRunnable will be reset and the WebView
destroyed. Check for a null mRunnable before accessing mWebView.
Bug: 3361009
Bug: 3349815
Change-Id: Idd9a2b788673d9ec95bfa083a4af7df705c22fcd
|
| |
|
|
|
|
| |
Also delay dismissing the dialog to avoid flashing it briefly.
Change-Id: I86c23ccebc6ccaad1feac56bea4ddcfefe1607f4
|
|
|
On startup, attempt to log the user into google sites. Show a progress dialog
that the user can cancel if login takes too long.
Add a new preference for toggling auto signin. This preference shows the
current account and allows the user to choose the account to use. If there are
no accounts, the option is disabled. The saved account is validated each time
it is accessed in case the account was removed.
Bug: 3278072
Change-Id: I10ce1dc57a683b2820b17ef6955577037c82f332
|
