1504657 - Site keeps loading in firefox.

Status: RESOLVED FIXED

(Web Compatibility :: Site Reports, defect, P1)

Description

[martin84a]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0

Steps to reproduce:

1) Go to www.jp.dk (A website for a major Danish newspaper)
2) Select an article and wait for the page to finish loading
3) Try to browse back 


Actual results:

When trying to browse back, the page loads forever. On Chrome I have no issue.

Comment 1

[Mira Lobontiu (Android QA)]

Hi Martin,

Environment: 
Device: Samsung Galaxy Note 8 (Android 8.0)
Build: Firefox Nightly 65.0a1 (2018-11-04)

I could reproduce the issue following your steps. Also reproducible on Beta 64.0b6 and Release 62.0.3.

Thank you for the report!

Comment 2

[Kevin Brosnan [Ex-Mozilla]]

Suspected webcompat. Mike would you have a look?

Comment 3

[Mike Taylor [:miketaylr]]

I can reproduce in Desktop with Responsive Design Mode, if I sent a Firefox for Android UA string.

Tom, can you sniff it out? Seems scripty -- I don't see anything weird at the HTTP level.

Comment 4

[Thomas Wisniewski [:twisniewski]]

It's this fragment of code in their markup (https://jyllands-posten.dk/?device=mobil):

><input type="hidden" id="cacheTest"/>
><script>
>  (function () {
>    var input = document.querySelector('#cacheTest');
>    if (input.value !== '') {
>      window.location.reload();
>    }
>    input.value = "cached";
>  }());
></script>

This would be site error, because they aren't telling the reload() method to actually ignore the browser cache (so the input always has the value "cached" no matter how many times they call reload).

Changing it to pass true fixes the issue in local tests:

>    if (input.value !== '') {
>      window.location.reload(true);
>    }

Comment 5

[Mike Taylor [:miketaylr]]

Thanks Tom.

Adam, can we try to reach out to the site about Comment #4?

Comment 6

[Adam Stevenson [:adamopenweb]]

Reaching out to customer support:
http://abonnement.jyllands-posten.dk/kundecenter

Comment 7

[martin84a]

Is this a case of Chrome not following proper web-standards since the script doesn't act the same with Chrome? If so I'm getting flashback to IE6 where developers just made sure that it worked in IE6 no matter how poor that browser was at following web-standards.

Comment 8

[Firefox Bug Husbandry Bot]

See bug 1547409. Moving webcompat whiteboard tags to keywords.

Comment 9

[Jeroen Kruis]

The offending code is no longer present.