diff options
author | Andy Huang <ath@google.com> | 2012-11-05 14:57:16 -0800 |
---|---|---|
committer | Andy Huang <ath@google.com> | 2012-11-05 14:57:16 -0800 |
commit | 69aecc996f92521e3b2e1a11f7d3797227868cf2 (patch) | |
tree | 0b493a8846a0d7d2cf51e24abcd64b546379a210 /assets | |
parent | 93dc202420c3bf8adf4d9e8ae18c8e30e3cb1959 (diff) | |
download | android_packages_apps_UnifiedEmail-69aecc996f92521e3b2e1a11f7d3797227868cf2.tar.gz android_packages_apps_UnifiedEmail-69aecc996f92521e3b2e1a11f7d3797227868cf2.tar.bz2 android_packages_apps_UnifiedEmail-69aecc996f92521e3b2e1a11f7d3797227868cf2.zip |
speculative fix for native WebView crashes
Towards the end of MR1, we saw more native crashes on
conversation load. It's possible it was purely due to increased
testing, but just in case it was due to loading animation
changes, go back to Gmail1-style content-ready code.
The document has a small div that initially has an
"initial-load" class set on JB+. The class is no longer
dynamically added in JS. The animation-start event listener
remains as-is, configured on DOM parse (and not later upon DOM
load).
Give the animation a different name from the CSS class that
triggers it, on the off-chance that this is crossing some wires.
Bug: 7370125
Change-Id: I4f0f807fbb9e32e024b6c74a6d9684e7fb337695
Diffstat (limited to 'assets')
-rw-r--r-- | assets/script.js | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/assets/script.js b/assets/script.js index 0fa68c1cc..fa0212201 100644 --- a/assets/script.js +++ b/assets/script.js @@ -301,7 +301,6 @@ function setupContentReady() { if (ENABLE_CONTENT_READY) { signalDiv = document.getElementById("initial-load-signal"); signalDiv.addEventListener("webkitAnimationStart", onContentReady, false); - signalDiv.classList.add("initial-load"); } } |