4 ms·

Just an update from the Google side: As discussed below, any Android users on 4.4+ or running Chrome are not affected. For earlier versions of Android, we've sh

Just an update from the Google side: As discussed below, any Android users on 4.4+ or running Chrome are not affected. For earlier versions of Android, we've shipped patches for AOSP: https://android.googlesource.com/platform/external/webkit/+/1368e05e8875f00e8d2529fe6050d08b55ea4d87 https://android.googlesource.com/platform/external/webkit/+/... https://android.googlesource.com/platform/external/webkit/+/7e4405a7a12750ee27325f065b9825c25b40598c https://android.googlesource.com/platform/external/webkit/+/... These are in the AOSP branches for jb-dev, jb-mr1-dev, jb-mr1.1-dev, and jb-mr2-dev.

junktest 12y ago
is android kitkat 4.4.x safe from this bug regardless of whether chrome browser exists (not installed or uninstalled) in the phone or not? please enlighten. thanks.
- joev_ 12y ago
  My understanding is that Chrome replaced Webkit in WebView's internal implementation in 4.4, so the bug should never appear in 4.4.
  - paulirish 12y ago
    Yup correct. Completely different WebView. And the bug is technically in the WebView.
schwarze_pest 12y ago
Does this mean that there will be an update for the Galaxy Nexus?
- aiiane 12y ago
  OS updates for $SPECIFIC_PHONE are generally reliant on the carrier to decide to push out a patch, even after AOSP itself is patched. So an answer "from the Google side" can't really answer your question.
  - schwarze_pest 12y ago
    The regular carrier-independent versions (Yakju/Maguro and Takju/Maguro) which are directly supported by Google.