dahamsta Posted May 20, 2015 Report Share Posted May 20, 2015 If i have more than 2 async tags on one page, it causes page reloads or history additions (I'm not sure which) in Firefox. For example, this page has two ads enabled, one below the navbar and one above the footer, and everything works fine. I've enabled a third on the archive pages though, and if I right-click the Back button in Firefox the current page appears twice, and two clicks are needed to go back. I don't see anything obvious in the error console. Any ideas? Do I need to switch back to JS tags? Quote Link to comment Share on other sites More sharing options...
dahamsta Posted May 22, 2015 Author Report Share Posted May 22, 2015 Just me then? Quote Link to comment Share on other sites More sharing options...
Matteo Beccati Posted May 26, 2015 Report Share Posted May 26, 2015 I can't replicate with Firefox on your own site, performing the actions you suggested. Quote Link to comment Share on other sites More sharing options...
dahamsta Posted May 26, 2015 Author Report Share Posted May 26, 2015 I had to switch back to JS tags. Quote Link to comment Share on other sites More sharing options...
frEEk Posted September 24, 2015 Report Share Posted September 24, 2015 Same behaviour confirmed here. Only happens in FF, and does not happen with non-async JS tags. Current install (3.2.1). It doesn't seem to stack in the history, oddly. ie. start on homepage, see 1 or 2 (can't tell what causes the random choice of how many) extra history entries. Navigate to a new page, new page has 1 or 2 extra entries but the previous page now just shows the one entry.My guess is this is a bug in FF, but maybe something that can be worked around easily?Can view the issue on bigclassaction com and am happy to make tweaks on the site to help debug. Quote Link to comment Share on other sites More sharing options...
frEEk Posted October 22, 2015 Report Share Posted October 22, 2015 This is a significant issue given FF has a significant browser share. We will have to lose the async tags if this can't be solved, which is a damn shame cause they sure help pagespeed times. Quote Link to comment Share on other sites More sharing options...
Matteo Beccati Posted October 22, 2015 Report Share Posted October 22, 2015 @frEEK Could you please provide a small test page that shows the issue? Despite multiple tries we haven't been able to replicate the issue. Quote Link to comment Share on other sites More sharing options...
Richard Foley Posted October 22, 2015 Report Share Posted October 22, 2015 (edited) I'm not seeing this behaviour with multiple asynchronous tags on a single page, also using Firefox. No problems seen at all (just FYI). Edited October 22, 2015 by Richard Foley Quote Link to comment Share on other sites More sharing options...
frEEk Posted October 22, 2015 Report Share Posted October 22, 2015 You can see the behaviour on bigclassaction.com. I just confirmed yesterday that it is still happening. It does _not_ happen on a page that doesn't have any ads like https://www.bigclassaction.com/evaluation.phpFF only. Exact same pages in Chrome don't display this effect. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.