I’ve also got uBlock enabled and the page works for me, but it’s worth giving a go just in case yours is set up differently.
Tried that (add-ons uBlock and Adblocker disabled): same results. Obviously James Evans’ post explains that this is now a “known issue”.
Also tried Chrome: correct results, i.e. the issue is Firefox-specific.
A few weeks ago, we started receiving reports through our contact centre of the behaviour in Journey Planner you mentioned.
The response to this reported glitch has not been adequate: the glitch with uBlock Origin/Adblock Ultimate should have been investigated very quickly and then, well before actually finding a solution, your development team should have put a very clear banner or similar, for Firefox users, saying “this tool may not work with Firefox using add-on uBlock/Adblock Ultimate… we are working on a solution”.
Why didn’t you do this? Why don’t you do it now?
(Though in fact I obviously still seem to be getting incorrect results even with these add-ons disabled: so until further notice and subject to further testing it seems that this banner should be displayed for ALL Firefox users…)
I confirm that I started noticing this malfunctioning many weeks ago now.
After further testing
By disabling all add-ons (I had 3, the 3rd being one called “I still don’t care about cookies”: avoids tiresome GDPR-style requests for consent of the kind alluded to), and after deleting and creating my cookie for TfL, I get correct results with Firefox. I’m going to add back those add-ons one by one …
… and further …
It now seems that “I still don’t care about cookies” may be the culprit. It appears to be a fairly innocuous thing, but my provisional belief is now that it reacts very badly with this “Cookiebot” tool. Therefore the banner I suggested should probably read “this tool may not work with Firefox using add-on ‘I still don’t care about cookies’”. This add-on is quite niche however. I am not aware of it ever having caused any problems hitherto, although in the reviews on its homepage there are a few reports of some websites having problems with it.
To me it sounds like “Cookiebot” may be rather too aggressive (and/or unintelligent), and may be interfering with other cookie-related add-ons by the sound of these other reported problems… Obviously the correct way Cookiebot should interact with “I still don’t care…” should be: “Do you give consent?”, “Yes”, “OK”. As I say, I am not aware of any of the many thousands of websites I have visited since installing “I don’t care…”/“I still don’t care…” ever once having had problems with it.
Finally: the fact that the malfunctioning presumed to be due to the Cookiebot+“I still don’t care” combination doesn’t actually stop the app functioning, but instead delivers erroneous results is a software fault in itself which needs resolving. Why would a failure to ascertain consent lead to results saying “Duh, you can cycle or walk if you want …”? It should either make it fail or not fail. I suspect the deficiency there may be quite easy to identify in the JP code*. Please resolve it.
* …could it be a case of some super-simple JS script which doesn’t actually need to query any databases, just calculating walking/cycling times on the basis of geographical distances? Apart from being misleading and baffling in the cited circumstances, that also still shouldn’t function if the user has not given GDPR-style consent.