John,
The android-x86 group have tried switching to chromium, but it appears to have
a dependancy on the v8 engine which in turn requires the ARM platform (see
http://groups.google.com/group/android-x86/msg/f99f379337585667 for details).
Do you have a recommendation for what groups porting to non-ARM platforms
should do?
Al.
--
T: @alsutton W: www.funkyandroid.com
The views expressed in this email are those of the author and not necessarily
those of Funky Android Limited, it's associates, or it's subsidiaries.
On 11 Jan 2012, at 21:16, John Reck wrote:
> Yes, this is the right fix. However, you should consider this stack
> deprecated and switch as soon as possible to the Chromium HTTP stack. This
> method is only used in the Apache HTTP stack path. I would not be surprised
> if other aspects of the Apache stack are broken or missing features.
>
> The change I submitted to master that hasn't been pushed yet is:
>
> --- a/core/java/android/webkit/BrowserFrame.java
> +++ b/core/java/android/webkit/BrowserFrame.java
> @@ -870,6 +870,7 @@ class BrowserFrame extends Handler {
> loader.setCacheMode(headers.containsKey("If-Modified-Since")
> || headers.containsKey("If-None-Match") ?
> WebSettings.LOAD_NO_CACHE : cacheMode);
> + loader.executeLoad();
> // Set referrer to current URL?
> return !synchronous ? loadListener : null;
> }
>
> --
> unsubscribe: android-porting+unsubscr...@googlegroups.com
> website: http://groups.google.com/group/android-porting
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
