summaryrefslogtreecommitdiffstats
path: root/android_webview/native/aw_settings.h
Commit message (Collapse)AuthorAgeFilesLines
* OffscreenPreRaster and its plumbingshush2015-02-251-0/+1
| | | | | | | | | | | | | | | If OffscreenPreRaster is enabled, the viewport rect for tile priority and the tile memory limit calculation will be based on the size of the webview, instead of the size of visible area of the webview. Design doc here https://docs.google.com/document/d/1xOMjvbEIS3dMzpWXWrsl7qV8QOgGEIZL1QxgnfOXmq4/ BUG=460638 Review URL: https://codereview.chromium.org/944053004 Cr-Commit-Position: refs/heads/master@{#318126}
* Update {virtual,override,final} to follow C++11 style.dcheng2015-02-041-4/+3
| | | | | | | | | | | | | | | | The Google style guide states that only one of {virtual,override,final} should be used for each declaration, since override implies virtual and final implies both virtual and override. This patch was automatically generated with an OS=android build using a variation of https://codereview.chromium.org/598073004. BUG=417463 R=michaelbai@chromium.org Review URL: https://codereview.chromium.org/893343002 Cr-Commit-Position: refs/heads/master@{#314487}
* Remove most native WebContents references from Javadtrainor2015-01-271-1/+1
| | | | | | | | | | | | - Make all Tab#initialize(0 methods take a WebContents instead of a native WebContents pointer or a ContentViewCore. - Make ContentViewCore#initialize() take a java WebContents - Update methods in ContentViewUtil to no longer expose native WebContents. - Add WebContents#destroy() to handle deleting a native WebContents and Java WebContents object. - Remove many other references that cascade from these changes. Review URL: https://codereview.chromium.org/831523005 Cr-Commit-Position: refs/heads/master@{#313338}
* replace OVERRIDE and FINAL with override and final in android_webview/mostynb2014-10-071-2/+2
| | | | | | | | BUG=417463 Review URL: https://codereview.chromium.org/623833003 Cr-Commit-Position: refs/heads/master@{#298465}
* aw: Only enable webgl on hardware webviewboliu@chromium.org2014-07-101-2/+0
| | | | | | | | | | Also clean up 2d canvas code to respect command line switches. BUG=392663 Review URL: https://codereview.chromium.org/375193002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@282220 0039d316-1c4b-4281-b951-d872f2087c98
* Move webpreferences.* from webkit/ to content/tfarina@chromium.org2014-07-091-1/+3
| | | | | | | | | | | | | BUG=338338 TEST=None R=jam@chromium.org TBR=boliu@chromium.org # for android_webview TBR=bauerb@chromium.org # for components/plugins TBR=dmichael@chromium.org # for ppapi Review URL: https://codereview.chromium.org/357203003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@281978 0039d316-1c4b-4281-b951-d872f2087c98
* We have a problem in the process on destroying WebContentsImpl becausezverre@yandex-team.ru2014-05-091-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | each WebContentsObserver first NULLs its web_contents_ pointer and performs cleanup code after that. This could work if we guaranteed that every WebContentsObserver doesn't directly or indirectly affect any other WebContentsObserver. But actually WebContentsObservers can do anything and also affect each other. And if one WebContentsObserver already NULLed its web_contents_ pointer (e.g. ZoomController) other WebContentsObserver (e.g. InterstitialPageImpl) calls it (indirectly in this case) we have problems and result depends on ordering of WebContentsObservers in the list of observers. The solution splits that process into two phases. First we let each WebContentsObserver to perform their cleanup code and at that point they can freely call each other, we completely don't care about the ordering. We can call this phase as untrusted phase because we deal with some cleanup code that can do anything. After that we make second pass and NULL each web_contents_ pointer and this phase is trusted because we call only private implementation of WebContentsObserver that we definitely can trust. BUG=363564 Review URL: https://codereview.chromium.org/257153003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@269264 0039d316-1c4b-4281-b951-d872f2087c98
* [Android WebView] Add an api to control the hole punching.ycheo@chromium.org2014-04-241-3/+3
| | | | | | | | | | | | - Add a method to AwSettings. - Add a flag to RendererPreferences. - Make WebMediaPlayerAndroid to punch the hole depends on the flag. BUG=329447 Review URL: https://codereview.chromium.org/236133010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@265885 0039d316-1c4b-4281-b951-d872f2087c98
* Rename jni_helper.h to jni_weak_ref.h.newt@chromium.org2014-04-231-1/+1
| | | | | | | | | BUG=365021 TBR=darin Review URL: https://codereview.chromium.org/247263009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@265715 0039d316-1c4b-4281-b951-d872f2087c98
* [Android WebView] Fix thread unsafety in accessing Java side gettersmnaganov@chromium.org2014-01-311-0/+1
| | | | | | | | | | | | Re-route calls to AwSettings::PopulateWebPreferences through Java to acquire mAwSettingsLock. Add assertions on holding the lock into getters called from native code. BUG=337112 Review URL: https://codereview.chromium.org/143803016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@248279 0039d316-1c4b-4281-b951-d872f2087c98
* [Android WebView] Turn on accelerated canvas based on View.isHardwareAcceleratedboliu@chromium.org2014-01-171-0/+2
| | | | | | | | | | | | | | | In onAttachedToWindow, check that if the view is hardware accelerated, then enable hardware accelerated 2d canvas. Similarly disable canvas on detach. Note that accelerated 2d canvas is still off by default, but this patch adds a command line switch to turn it on. BUG=332273 Review URL: https://codereview.chromium.org/140753006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245648 0039d316-1c4b-4281-b951-d872f2087c98
* Android: moves android_webview/ to use long for JNI.bulach@chromium.org2013-11-281-1/+1
| | | | | | | | BUG=317523 Review URL: https://codereview.chromium.org/83203002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@237788 0039d316-1c4b-4281-b951-d872f2087c98
* [Android WebView] Disable shrinksStandaloneImagesToFitboliu@chromium.org2013-10-071-0/+3
| | | | | | | | | | | | If shrinksStandaloneImagesToFit is true, then it breaks single image documents in wrap contents mode. BUG= NOTRY=true Review URL: https://codereview.chromium.org/26207002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@227261 0039d316-1c4b-4281-b951-d872f2087c98
* Currently Android WebView will push settings from the java side to the ↵benm@chromium.org2013-09-271-0/+6
| | | | | | | | renderer, but if the browser needs to read those settings back we will use a default set from WebContentsImpl as we neglect to override ContentBrowserClient::OverrideWebKitPrefs. This means that the browser and renderer can see out of sync preference values. Review URL: https://codereview.chromium.org/23619089 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225611 0039d316-1c4b-4281-b951-d872f2087c98
* Use contents size for android_webview layout size.mkosiba@chromium.org2013-09-181-1/+0
| | | | | | | | | | | | | | | | Currently android_webview uses RenderView::preferredSize (which is based off of documentElement.height) to drive the android.view.View layout size. WebViewClassic would use content size for that purpose which meant that absolute-positioned elements can cause the Classic WebView to grow. This CL makes AwContents use the contents size for driving layout. BUG=286336 Review URL: https://chromiumcodereview.appspot.com/23899004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@223984 0039d316-1c4b-4281-b951-d872f2087c98
* Fix Popup window flow to work with synchronous compositor gfx modejoth@chromium.org2013-06-141-2/+3
| | | | | | | | | | | | | | | | | | This switches around the object lifetimes, so WebContents and AwContents (native) have identical lifetimes, but now the native AwContents may exist before its java counterpart, and in the popup flow the java object may switch from its default peer instance to acquire the pop-up AwContents/WebContents instead. Additionally, makes some simplifications to the way AwSettings is created and also fixes a potential leak (the native instance was never deleted if destroy() was not called). NOTRY=true BUG=245801 Review URL: https://chromiumcodereview.appspot.com/16843008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@206516 0039d316-1c4b-4281-b951-d872f2087c98
* Implement get/set(saveformdata) for chromium based webview.sgurun@chromium.org2013-05-151-0/+1
| | | | | | | | BUG=b/6335434 Review URL: https://chromiumcodereview.appspot.com/14637009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@200197 0039d316-1c4b-4281-b951-d872f2087c98
* [Android WebView] Remove direct access to fields in aw_settingsmnaganov@chromium.org2013-05-101-11/+7
| | | | | | | | | | | | As per Marcus' proposal, replace direct access to Java object fields with getter methods. This is less error-prone and leverages facilities of automatic JNI code generation. BUG=b/8296421 Review URL: https://chromiumcodereview.appspot.com/14698004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@199456 0039d316-1c4b-4281-b951-d872f2087c98
* [Android WebView] Move the most of WebSettings into AwSettingsmnaganov@chromium.org2013-04-251-10/+13
| | | | | | | | | | | | | | | | Historically, WebSettings management is used to be in the ContentSettings class, while only WebView actually needs it. Chrome for Android is only interested in the value of the "JavaScript enabled" setting. This change leaves zoom-related settings intact, as moving them will require decoupling of the ZoomManager class from the ContentView* family of classes, which deserves a separate change. BUG=b/8296421 Review URL: https://chromiumcodereview.appspot.com/14271024 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@196399 0039d316-1c4b-4281-b951-d872f2087c98
* [android] Resize the android_webview if it's 0x0 initially.mkosiba@chromium.org2013-04-191-0/+3
| | | | | | | | | | | | | | | | This changes the content size update path for android_webview to use the preferred size RenderView mechanism instead of the CompositorFrameMetadata. The reason for the change is due to the fact that the CompositorFrameMetadata is not updated when the view size is 0x0, which is a common use case for the WebView when it's layout mode is set to "wrap content". BUG=b/8187850 TEST=AndroidWebViewTests Review URL: https://chromiumcodereview.appspot.com/12567020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@195135 0039d316-1c4b-4281-b951-d872f2087c98
* [Android WebView] Never turn off viewport and fixed layoutmnaganov@chromium.org2013-04-171-3/+0
| | | | | | | | | | | This is to avoid skipping "meta viewport" tag processing. For controlling wide viewport-related behavior, a corresponding WebSetting has been added into Blink. Review URL: https://codereview.chromium.org/14234002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@194576 0039d316-1c4b-4281-b951-d872f2087c98
* [Android WebView] Expose resetScrollAndScaleState from AwSettingsmnaganov@chromium.org2013-02-281-0/+1
| | | | | | | | | | As joth@ has suggested, let's not expose AwContents to ContentSettingsAdapter, so make resetScrollAndScaleState available on AwSettings instead. Review URL: https://chromiumcodereview.appspot.com/12374012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@185334 0039d316-1c4b-4281-b951-d872f2087c98
* [Android WebView] Implement WebView.setInitialScalemnaganov@chromium.org2013-02-281-0/+3
| | | | | | | | | | WebView.setInitialScale allows to set up the initial page scale which overrides viewport meta tag settings. Review URL: https://chromiumcodereview.appspot.com/12315104 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@185236 0039d316-1c4b-4281-b951-d872f2087c98
* [Android WebView] Update WebView.EnableFixedLayoutMode in sync with ↵mnaganov@chromium.org2013-02-271-0/+6
| | | | | | | | | | | | | | | | | | | ViewportEnabled After WebKit http://trac.webkit.org/changeset/143735, WebView.EnableFixedLayoutMode must be updated together with WebSettings.ViewportEnabled. This is a temporary state of affairs, one of these settings will be removed in future. Only Android WebView needs to switch thid mode dynamically, thus the change is implemented in the android_webview layer. BUG=177684 Review URL: https://chromiumcodereview.appspot.com/12317071 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@185016 0039d316-1c4b-4281-b951-d872f2087c98
* [Android WebView] Implement WebSettings.setTextZoom for legacy layout modesmnaganov@chromium.org2013-02-141-0/+41
We rely on the fact that on Android, page scaling factor isn't used for page zooming, so text scaling can be used (unlike desktop Chrome). Review URL: https://chromiumcodereview.appspot.com/12220012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@182481 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-11 11:01:34 +0000