JavaScript & jQuery not running - Onload or Procedural
Reported by
dkowa...@mdvip.com,
Mar 10 2016
|
|||||||||||
Issue description
Steps to reproduce the problem:
1. Hide element until load completes
2. Remove element by id
3. Scroll to element by id
What is the expected behavior?
Remove element by id
Scroll and call execute actions but it is not working onload or by procedural
What went wrong?
I believe the JavaScript is being passed to graphics accelerator and async calls aren't running.
//Temp Hide Content Until Loads
$('head').append('<style id="tempHide" type="text/css">#myID { visibility:hidden; }</style>');
window.onload = function () {
//Unhide CSS Element by Removing
$('#myID').remove();
//Scroll down to element by id; doesn't run on Chrome running on latest Android OS.
$('html, body').animate({ scrollTop: $('#myID').offset().top }, 'slow');
};
Did this work before? N/A
Chrome version: 48.0.2564.116 Channel: stable
OS Version: Any
Flash Version: Shockwave Flash 21.0 r0
Please contact me if you have any questions or further understanding why Chrome on Android is the only problem. This was only testing on Samsung devices
Galaxy Note 4
Galaxy Edge 7 (latest)
,
Mar 10 2016
JQuery Code:
setTimeout(function(){
$('#tempHide').remove();
}, 20000);
//Temp Hide Content Until Loads
$('head').append('<style id="tempHide" type="text/css">#myID { visibility:hidden; }</style>');
<script type="text/javascript">
setTimeout(function(){
$('#preloadImageSrc').attr('src', preloadImageNewSrc);
$('#preloadImageLink').html('Retry');
$('#tempHide').remove();
setTimeout(function(){
$('#preloadImage').fadeOut();
}, 30000);
setTimeout(function(){
$('#preloadImage').remove();
}, 32000);
}, 20000);
$('body').append('<div id="preloadImage" style="background-color: white; position:fixed; z-index: 99999; right: 10%; bottom: 50%; margin-top:15%; opacity: 0.80; filter: alpha(opacity=80); -webkit-border: 50%; -moz-border: 50%; border-radius: 50%;"><img id="preloadImageSrc" style="width:128px; height:128px;" src="loading.png” alt="Loading Form" title="Loading Form" /><a id="preloadImageLink" href="#myID" style="position:absolute; z-index: 99998; left:40%; top: 65%; opacity: 0.80; filter: alpha(opacity=80); font-weight:bold; "></a></div>').fadeIn();
</script>
<script type="text/javascript">
window.onload = function () {
//Delay Visibility Until Form Completes Load & Focus View to - First Input Box in Element
$('#myID').delay(1500).fadeIn(500).delay(1000).focus();
//Unhide Element
$('#tempHide').remove();
//Scroll To The myID Element
$('html, body').animate({ scrollTop: $('#myID').offset().top }, 'slow');
//Allow page to load and remove preload image
setTimeout(function(){
$('#preloadImage').fadeOut();
setTimeout(function(){
$('#preloadImage').remove();
}, 5000);
}, 1000);
};
</script>
Generated Source Code in Header:
<head>
<style id="tempHide" type="text/css">#myID { visibility:hidden; }</style>
</head>
<body>
...
</body>
,
Mar 10 2016
<body><div id="myID">...</div></body>
,
Mar 14 2016
Thank you for providing more feedback. Assigning to requester "dglazkov@chromium.org" for another review. For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 14 2016
I may have communicated this too vaguely. What I am looking for is actual files I can download and run to see the problem. I am not sure what to do with the code that you provided in the comments. Could you attach the html/js files to the bug? :)
,
Mar 14 2016
I have emailed you directly, thank you.
,
Mar 15 2016
We discussed over email privately. Until there's a simpler reduction, it is unclear whether the issue is actually a Blink bug. Leaving open in case reporter wants to pursue creating a reduction.
,
Mar 15 2016
,
Mar 15 2016
Thank you for providing more feedback. Assigning to requester "dglazkov@chromium.org" for another review. For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 15 2016
LOL, sheriffbot. Marking as WontFix.
,
Mar 17 2016
I wanted to give you additional feedback on the issue that was determined on the Chrome browser. It is related to mixed content, the issue is a Google Tag manager tracking pixel not being incorporated as SSL. Even if the page loads as non-secure [http], some elements on the page [iframe and other tracking] are retrieving resourcing using SSL. That seems to be not allowing Chromium on Android devices to load the page properly. I find that weird because the page is loaded as non-secure and would only expect this issue with loading a secure and having insecure elements breaking the page load and not the other way around. ~Daniel Kowalec
,
Mar 17 2016
Hmm, weird. Mike, could you help dkowalec@ figure out what's going on?
,
Mar 17 2016
dkowalec@: Hi! Is there a page I could look at? It's not clear to me from the description what's going on. I guess this is a repeat of dglazkov@'s request for a reproducible reduction. :)
,
Mar 17 2016
Also: Are there console errors that lead you to believe that mixed content checking is doing the wrong thing?
,
Mar 17 2016
No specific errors stating mixed content; otherwise I wouldn't have had to do the investigation. However, testing before and after removing the Google Tag tracking sped things up. Once that was changed, the issue seems resolved. I don't need additional investigation just curious as this why this was so. Have a good day.
,
Mar 23 2016
,
Apr 29 2016
Closing as per #15.
,
Feb 6 2017
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by dglazkov@chromium.org
, Mar 10 2016