Do either of these typical troubleshooting steps make any difference?

When you have a problem with one particular site, a good "first thing to try" is clearing your Firefox cache and deleting your saved cookies for the site.

(1) Bypass Firefox's Cache

Use Command+Shift+r to reload the page fresh from the server.

Alternately, you also can clear Firefox's cache completely using:

"3-bar" menu button (or Firefox menu) > Preferences > Advanced

On the Network mini-tab > Cached Web Content : "Clear Now"

If you have a large hard drive, this might take a few minutes.

(2) Remove the site's cookies (save any pending work first). While viewing a page on the site, try either:

• right-click and choose View Page Info > Security > "View Cookies"
• (menu bar) Tools > Page Info > Security > "View Cookies"
• click the globe or padlock to the left of the address in the address bar > More Information > "View Cookies"

In the dialog that opens, you can remove the site's cookies individually.

Then try reloading the page. Does that help?

In case one of your extensions is involved, could you test the page in Firefox's Safe Mode? That's a standard diagnostic tool to deactivate extensions and some advanced features of Firefox. More info: Diagnose Firefox issues using Troubleshoot Mode.

You can restart Firefox in Safe Mode using either:

• "3-bar" menu button > "?" button > Restart with Add-ons Disabled
• Help menu > Restart with Add-ons Disabled

Not all add-ons are disabled: Flash and other plugins still run

After Firefox shuts down, a small dialog should appear. Click "Start in Safe Mode" (not Reset).

Any difference?

I tried the options you suggested but there was no change. I am also working on a mac, not a pc, if this makes a difference.

Firefox 33 is just rolling out and I think this is the only SharePoint issue I've seen so far.

Are your fellow Firefox users also getting the same issue or are there any differences?

Is your SharePoint on a secure server (HTTPS address)? Just wondering whether a security-related change could be affecting the site.

Yes, all firefox users are having the same issues. There was a code someone shared with us and it seemed to work for maybe a month or so.

I'm going to assume that we are on a secure server.

Regarding the secure server, let me be more specific: does the address start with HTTP or HTTPS?

Now I'm curious about the code you were using before: was that a settings change you made in Firefox or something else?

Ah, so it looks like it starts with HTTP

I have attached a screen shot for both of your questions. Hopefully this will help!

Off the top of my head, I can't think of any changes in Firefox 33 that would affect SharePoint with an HTTP address.

While waiting for more feedback here, it might be worth keeping an eye on Microsoft's forums, too. This targeted Google search currently isn't returning anything that looks immediately relevant:

https://www.google.com/search?q=site%3Amicrosoft.com+%22sharepoint%22+%22firefox+33%22&tbs=qdr:m (latest month results only)

okay thanks! I'll keep checking back.