Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Australian Government official Bureau of Meteorology website does not load properly

  • 4 replies
  • 3 have this problem
  • 8 views
  • Last reply by dennis_j

dennis_j
dennis_j
more options

The following page from the Australian Government official Bureau of Meteorology website does not load properly http://www.bom.gov.au/australia/meteye/?lat=-23.7&lon=133.87&url=/nt/alice-springs/&name=Alice+Springs

It spins forever never completely loading, and never reaching a point of being usable, for example, try accessing the UV information link.

The page works fine in webkit based browsers like https://wiki.gnome.org/Apps/Web Web 3.14.1 Powered by WebKit 2.6.2 It used to work fine in previous versions of Firefox.

Current version I'm using, in which it fails to load is: version 57.0 update channel: release updates: automatic

thanks Dennis

The following page from the Australian Government official Bureau of Meteorology website does not load properly http://www.bom.gov.au/australia/meteye/?lat=-23.7&lon=133.87&url=/nt/alice-springs/&name=Alice+Springs It spins forever never completely loading, and never reaching a point of being usable, for example, try accessing the UV information link. The page works fine in webkit based browsers like https://wiki.gnome.org/Apps/Web Web 3.14.1 Powered by WebKit 2.6.2 It used to work fine in previous versions of Firefox. Current version I'm using, in which it fails to load is: version 57.0 update channel: release updates: automatic thanks Dennis

Chosen solution

If you use extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) that can block (wanted) content (e.g. Adblock Plus, NoScript, Ghostery, uBlock Origin) always make sure such extensions do not block (wanted) content.

  • make sure your extensions and filters are updated to the latest version
Read this answer in context 👍 1

All Replies (4)

FredMcD
FredMcD
more options

Are you blocking content?

Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.

A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?

alan_r
alan_r
more options

For the record it works fine for me from another part of Australia on W10 and Fx 57.

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Chosen Solution

If you use extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) that can block (wanted) content (e.g. Adblock Plus, NoScript, Ghostery, uBlock Origin) always make sure such extensions do not block (wanted) content.

  • make sure your extensions and filters are updated to the latest version
dennis_j
dennis_j Question owner
more options

All three responses were very helpful.

  1. In the end I went to the menu, New Fx Menu > chose 'Help' Help-29 > then 'Restart with Add-ons disabled...' as suggested by FredMcD.
  2. The site then worked fine, as noted by alan_r.
  3. I then went through my extensions one by one until I found uBlock Origin was causing the problem, as hypothesised by cor-el.
  4. I disabled this extension for this particular web page, et Voila! I'm happily using 'MetEye' to keep up with UV radiation situation again ('extreme' during most of the day where I am).

Thanks everyone for such quick and helpful responses! I started to try to click all responses as 'solving' the issue, but the system did not allow such an action on my part, so I had to chose just one.