| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Bug: 10427705
Allows Browser to compile even when WebViewClassic is no longer in
frameworks/base. The deleted functionality was already disabled at
runtime when using non-classic webview.
Change-Id: I21b58ec52ac059c699b49a2dd80008d9a9e6791a
|
|
|
|
|
|
|
|
| |
Has to escape out to WebViewClassic whenever it needs a hidden API.
Interdepends on https://android-git.corp.google.com/g/165608
Change-Id: Ic61dd7f57f75381864075605d5901f2688648cbd
|
|
|
|
|
|
|
|
| |
append an EXTRA_APPLICATION_ID field in the intent to navigate to
a new website, so that the browser won't open a new tab for every
new site
Change-Id: I69dddabeef83e124c43adab7bf3ed1e064b396ab
|
|
|
|
|
|
|
| |
WebView is complaining that some calls used in test app is not from
UI thread.
Change-Id: I7ef61694e3988a663eeedf03463580a93e57fe46
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Following the example of onReceivedSslError, implement onReceivedClientCertRequest
ERROR CASE CLIENT CERT CASE
<... From frameworks/base ...> <... From frameworks/base ...>
Tab.SubWindowClient.onReceivedSslError Tab.SubWindowClient.onReceivedClientCertRequest
Tab.mWebViewClient.onReceivedSslError Tab.mWebViewClient.onReceivedClientCertRequest
<... ssl_warnings dialog ...> <... KeyChain.choosePrivateKeyAlias/KeyChainLookup ...>
SslErrorHandler.proceed (with SslCertLookupTable) ClientCertRequestHandler.proceed (with SslClientCertLookupTable)
<... To frameworks/base ...> <... To frameworks/base ...>
Change-Id: I3ed3789c4efc97c87ab4773cdaed3e654a1fd1e3
|
|
|
|
|
|
|
|
|
| |
This is useful for testing, where crash recovery is handled by the
tests and also dialog interaction in undesirabls and also dialog
interaction in undesirable. Also included a minor unrelated change
to test app to handle/disable pop windows.
Change-Id: Iab337b31c803d50b74ba24ca80cc614fa752a846
|
|
|
|
|
|
|
|
|
| |
currently, if a page load ended up in Java crash, the crash will be
intercepted by test harness and during the test tearDown step, the
test status file will be removed, and the harness would think all
sites have been loaded successfully
Change-Id: Ifc02d7f4b7e76c8e8aad06fff273f9d61060874d
|
|
|
|
|
|
|
|
| |
this situation usually happens when WebView is spinning or
deadlocked on something, throwing a RuntimeException will
make this kind of error more noticeable
Change-Id: Id2f495494f67206830fd9d9e8a4bc2b175e82614
|
|
|
|
|
|
|
|
| |
some websites may trigger the browser to launch a non-http url.
typical case is that some website saw the client is Android, then
launch a market search urln to promote their native app.
Change-Id: I7785f66c8516a95597fd264b88f130008c309618
|
|
|
|
|
|
|
|
| |
* intercept JavaScript onUnload confirmation, no dialog shown
* using null download manager to avoid actual downloading during
random url test
Change-Id: I41758a87a0c5de5b42d34db8a403bb6d6ca053b2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are two reasons to use hardcoded external path as website
list: 1) the InstrumentationTestRunner did not provide a
mechanism for passing extra parameters down to test class, so
it's hard to provide test class with a location of test list file
in a parameter 2) if we include the test list file as part of the
asset and loaded via context during test, then it become hard for
test harness to inject a list at test execution time because test
list file is essentially compiled in when the apk is generated.
So I'm reverting the test list loading part back to previous
approach.
Change-Id: I5532de8d153172771dba160d6ad89092f81ec6e4
|
|
|
|
|
|
|
|
| |
Bug: 3248213
Fixes errors in the tests that were caused by missing files, proguard,
and the refactor.
Change-Id: I503dfc7ee42d0173e3a5ad032f58a6f4f310588c
|
|
|
|
|
|
|
| |
if it reads an empty line, or have reached end of file, it
will default to the start from beginning scenario.
Change-Id: Ife2e49bf8adf70d6caba7a1d65094401990325a2
|
|
|
|
|
|
|
|
| |
Currently the test does not increment page count after relaunched
after a crash. This means the crashed page will be loaded again,
causing a dead loop.
Change-Id: If4591fbd05521f0454151affafec09788e9208d9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* the definitive way to determine page load finish seems to be
onPageLoadFinished AND onProgressChanged==100, changing test
harness logic to reflect that
* webview does not seem to be happen if ClearCache is called too
often (or for certain pages?). It may complain that failed to
delete blahblah, then the test harness goes crazy. So changing
cache clear to after an entire iteration of web pages have been
loaded
* browser will load default home page, which may be disruptive
to the page load process. So for the test, the browser is now
started with initial intent to visit about:blank, which does
not trigger any page load at all
Change-Id: I1cfbd8d0196a05caea6a1c5137f45f1f59cc4c5f
|
|
|
|
|
|
|
| |
make the test fail gracefully instead of throwing exception. because
otherwise it interrupts test run.
Change-Id: Ia2b92355db83cd13c55263f0699b29c10e00ea96
|
|
|
|
| |
Change-Id: Ia10e72eec60d8c2155df95dec06334beb9feaab6
|
|
|
|
|
|
|
|
|
| |
* changed time recording unit from ns to ms
* implemented a timeout mechanism for page loading
* fixed a bug where url list will iterate forever
* minor changes in logging
Change-Id: I5f9812d2573d6942ddf404cf3fbb1782f328c73d
|
|
|
|
|
|
| |
parsable format.
Change-Id: Ia7f5f216d21925aebf5c807ee95036ebf6f6fa35
|
|
|
|
|
| |
- Refactoring test method to allow for optional looping and cache cleaning
- Adding test status output to resume + notify after a crash
|
|
Also patch makefiles to correctly build tests and allow for hidden API calls in test.
|