blocks|key|943016|text|我创建了一些类似的东西，我所需要的就是将它添加到我的WebView中|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|943017|android:layout_height="match_parent"|code-block|syntax|javascript|943018|entityMap^0|Q|7|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

I created something similar and all I needed was to add this to my <code>WebView</code>:

<pre><code>android:layout_height="match_parent"
</code></pre>

blocks|key|2085385|text|这对我来说很管用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2085386|<WebView
++++++++android:id="@%2Bid/wv"
++++++++android:layout_width="match_parent"
++++++++android:layout_height="match_parent"
++++++++android:scrollbars="horizontal"/>|code-block|syntax|javascript|2085387|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This works for me:

<pre><code>&lt;WebView
 android:id="@+id/wv"
 android:layout_width="match_parent"
 android:layout_height="match_parent"
 android:scrollbars="horizontal"/&gt;
</code></pre>

blocks|key|254288|text|这个问题似乎与硬件加速有关，如果API级别为>=+14，则默认启用硬件加速。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|254289|我有一个带有ScrollView的应用程序，它包含许多视图，我想将其作为一个类似于原始海报的单元滚动--其中一个视图是包装其内容的web视图。如果硬件加速启动，并且呈现的WebView非常复杂(图像、边框等)，则绘图缓存错误消息可以在LogCat中看到。有些屏幕有12项工作，而下一个屏幕有13项没有工作。我不认为改变的是项目的数量，而是最终呈现屏幕的复杂性。|offset|length|style|CODE|254290|症状通常是空白的WebView+-其他视图是视觉呈现和完全形成。偶尔，我会看到整个屏幕都是空白的，但这可能是在我对此提出各种建议的时候。|254291|人们并不总是能看到这一信息。例如，我在三星Galaxy4Mini上看到了运行4.2.2的问题，而在其他4.x设备上，比如我廉价的中国三星S3克隆版，运行4.1.2，一切都很好。我没有在任何1.x或2.x设备上见过它。|254292|我试着在视图层次结构中的各种视图和布局上选择性地关闭硬件加速，但是最后，由于沮丧和看到我浪费了多少时间来跟踪它，我只是在清单文件中对整个应用程序进行硬件加速。|254293|在关闭硬件加速之后，所有问题都消失了。在我的任何设备上，我都看不到明显的性能差异。假设1.x和2.x设备从一开始就没有使用过硬件加速，而我的4.x设备必须足够快才能处理软件渲染。不是说我的屏幕那么复杂。|254294|更新2015年4月|BOLD|254295|不幸的是，三星Galaxy4Mini在硬件加速关闭的情况下，已经恢复了4.4.2的警告信息。我有一个JavaScript面板打开/关闭动画的网络视图。除了初始布局(面板打开)引发这些警告外，一切正常，每次我关闭或打开面板时，我也会得到它们。这些警告现在只是恼人，应用程序运行良好。|254296|entityMap^0|0|6|A|2D|7|0|8|7|0|0|0|0|0|9|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@$D|Y|E|Z|F|G]|$D|10|E|11|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@$D|13|E|14|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|15|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|16|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|17|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|18|8|@$D|19|E|1A|F|R]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1B|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|V|$]]

The problem appears to be associated with hardware acceleration which is enabled by default if the API level is >= 14.

I have an app with a <code>ScrollView</code> that contains a number of views that I want to scroll as a single unit similar to the original poster - one of those views is a web view that wraps its content. If hardware acceleration is on and the rendered <code>WebView</code> is at all complex (images, borders, etc) then the drawing cache error message can be seen in LogCat. Some screen with 12 items worked while the next screen with 13 items did not work. I don't think that its the number of items that makes a difference, but the complexity of the final rendered screen.

The symptoms are typically a blank <code>WebView</code> - the other views are visually present and full formed. Very occasionally I see the whole screen blank, but that may have been while I was futzing with various suggestions found here on SO.

The message is not always seen. For example, I see the issue on a Samsung Galaxy 4 Mini running 4.2.2, while on other 4.x devices such as my cheap Chinese Samsung S3 clone running 4.1.2 everything is fine. I've not seen it on any 1.x or 2.x devices.

I tried to selectively turn off hardware acceleration on various views and layouts in the view hierarchy but in the end just turned of hardware acceleration for the whole app in the manifest file out of frustration and seeing how many hours I've wasted tracking this down.

After turning off hardware acceleration all issues have gone away. I see no noticeable performance differences on any of my devices. Presumably the 1.x and 2.x devices never used hardware acceleration in the first place, and my 4.x devices must be fast enough to cope with software only rendering. Not that my screens are that complicated.

Update APRIL 2015

Unfortunately the warning message is back on the Samsung Galaxy 4 Mini now running 4.4.2 even with hardware acceleration turned off. I have a webview with a JavaScript panel open/close animation. Everything works fine except that the initial layout (panel open) raises these warnings, and everytime I close or open the panel I also get them. These warnings are now just annoying, the app works fine.

blocks|key|2085445|text|webView.setLayerType(WebView.LAYER_TYPE_NONE,+null);|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2085446|为我工作过。根据硬件的不同，没有剩余的内存用于额外的屏幕外缓冲区，因为WebView完全是在嵌入到另一个滚动视图中时呈现的。|2085447|我认为这是Android中的一个缺陷，它不会自动回到这个选项中(速度更慢，但可以工作)。|2085448|entityMap^0|0|1G|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|P|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|K|$]]

<code>webView.setLayerType(WebView.LAYER_TYPE_NONE, null);</code>

worked for me. Depending on the hardware, there is no memory left for an additional off-screen buffer as the WebView is rendered entirely when embedded in another scroll view.

I consider it a bug in Android that it is not automatically falling back to this (slower, but working) option.

blocks|key|943120|text|正如其他答案所述，当硬件加速处于活动状态时，就会出现此问题。但对我来说，关闭整个应用程序的硬件加速并不是解决办法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|943121|我想我可以通过将android:layerType="software"设置为ScrollView来解决这个问题，这只会禁用ScrollView及其内容的硬件加速。|offset|length|style|CODE|943122|<ScrollView
++++android:layout_width="match_parent"
++++android:layout_height="match_parent"
++++android:layerType="software">

++++<LinearLayout
++++++++android:layout_width="match_parent"
++++++++android:layout_height="wrap_content"
++++++++android:orientation="vertical">

++++++++<FrameLayout
++++++++++++android:layout_width="match_parent"
++++++++++++android:layout_height="wrap_content">
++++++++++++...
++++++++</FrameLayout>

++++++++<WebView
++++++++++++android:layout_width="match_parent"
++++++++++++android:layout_height="wrap_content"+/>

++++</LinearLayout>

</ScrollView>|code-block|syntax|javascript|943123|请注意，这可能会带来负面的性能影响，因为在软件中呈现通常要慢一些。|943124|entityMap^0|0|8|S|13|A|1Q|A|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]|$D|U|E|V|F|G]|$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|Y|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|P|$]]

As the other answers stated, the issue appears when hardware acceleration is active. But turning off hardware acceleration for the whole app was no solution for me.

I figured I could solve the problem by setting <code>android:layerType="software"</code> to the <code>ScrollView</code>, which just disables the hardware acceleration for the <code>ScrollView</code> and its contents.

<pre><code>&lt;ScrollView
 android:layout_width="match_parent"
 android:layout_height="match_parent"
 android:layerType="software"&gt;

 &lt;LinearLayout
 android:layout_width="match_parent"
 android:layout_height="wrap_content"
 android:orientation="vertical"&gt;

 &lt;FrameLayout
 android:layout_width="match_parent"
 android:layout_height="wrap_content"&gt;
 ...
 &lt;/FrameLayout&gt;

 &lt;WebView
 android:layout_width="match_parent"
 android:layout_height="wrap_content" /&gt;

 &lt;/LinearLayout&gt;

&lt;/ScrollView&gt;
</code></pre>

Note that this may have negative performance implications, since rendering in software is usually slower.

I have a layout with a <code>ScrollView</code>, which contains the following views: <code>ImageView</code>, <code>TextView</code>, <code>WebView</code>, <code>TextView</code>. (This is because I would like to scroll the whole together, not just the contents of the <code>WebView</code>)

After loading some HTML in the <code>WebView</code>, I receive the following:

<pre><code>WARN/View(632): View too large to fit into drawing cache, needs 14236800 bytes, only 1536000 available
</code></pre>

...and the content of the <code>WebView</code> won't display. After removing the <code>ScrollView</code>, the warning disappears and all is well, except that I lose the wanted scroll functionality.

First: I know that trying to use a <code>ScrollView</code> inside another <code>ScrollView</code> is a bad thing in general, but I'm not 100% sure that in every case there's an equivalent solution without using <code>ScrollView</code>... I mean, of course one could put contents of <code>ImageView</code>s and <code>TextView</code>s into the <code>WebView</code>, but what about <code>Button</code>s or any other UI elements needing interaction? Is there a way in general which could solve issues like this without giving up the layout and scrolling everything at once?

I've found out that I'm not the only one with this issue. For other examples, check those questions - without working solution yet:

<ul>
<li><a href="https://stackoverflow.com/questions/15790317/webview-and-gridview-into-scrollview-view-too-large-to-fit-into-drawing-cache">WebView and GridView into ScrollView, View too large to fit into drawing cache</a></li>
<li><a href="https://stackoverflow.com/questions/17427673/android-view-too-large-to-fit-into-drawing-cache">Android - View too large to fit into drawing cache</a></li>
</ul>

WebView in ScrollView: "View too large to fit into drawing cache" - how to rework layout?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个ScrollView布局，它包含以下视图：ImageView、TextView、WebView、TextView。(这是因为我想把所有的内容一起滚动，而不仅仅是WebView的内容)在WebView中加载了一些HTML之后，我收到以下消息：WARN/View(632): View too large to fi...

问WebView in ScrollView：“查看太大而不适合绘图缓存”--如何重新设计布局？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WebView in ScrollView：“查看太大而不适合绘图缓存”--如何重新设计布局？EN