This occurs on Windows 8 64bit and Firefox 18/19 Beta. I have gone through many troubleshooting steps and it has made no difference in the slightest. I have cleared all caches several times, from inside Firefox and through 3rd party utilities. Tested in Safe Mode to no avail. Manually removed several add-ons, checked all add-ons are fully up-to-date (as always), and reset all Firefox settings to default (except Hardware Acceleration that causes graphics issues in 8 - does not help iCloud.com enabled, though). It works fully in all other browsers with similar add-ons without issue. I have not done a full, complete reset and profile removal - that is next. However, I have a gut feeling that is not the issue at hand. I performed a clean install of Windows 8 and a clean install of Firefox less than 2 weeks ago.
Solved! Go to Solution.
I may have be hasty in choosing a solution - I am unsure if this will work for everyone. I have not been able to recreate this issue anymore in Firefox 18.0.1 or 19 Beta 3. It was either fixed in 18.0.1 or was an issue with 3rd party software. The thing is, I'm the only user on my computer and I know EXACTLY what was installed or updated. There hasn't been any Windows Updates since January's Patch Tuesday, and I've tested several times since then with no luck (until Beta 3).
Downgrading from Beta 3 to 18.0.1 I did not do a clean install. I always did a clean install with fully removed profile and everything in previous tests, and it did not help the issue.
Basically, I'm completely stumped as to why it suddenly started working when Beta 3 is the only thing that's changed (I checked Windows Updates and restore points for any installs - nothing has changed since Patch Tuesday - I did not update any plugins for Firefox, but they never affected this bug active or disabled anyway). It is strange that downgrading does not reintroduce the bug, as I did previously have it in 18.0.1. So far, all I know is it does work in 19 Beta 3 again.
This could have been something simply fixed on Apple's website as well. It would explain why it works in 18 and 19 suddenly - when nothing else ever made a lick of difference. Hopefully someone else can confirm that is has started working for them as well!
I'm experiencing the exact same thing. I think my Firefox automatically upgraded to v18 yesterday and now I can't use iCloud mail at all. None of my mouse clicks register at all.
I'm running Firefox 18 on Windows 8 Professional 64-bit.
I'm kinda surprised this isn't a bigger issue yet, if it's not just me. Doing a Google for "Firefox iCloud compatible" returns this thread as the third result behind general Apple support pages. Hopefully this will be resolved soon, as I only use and recommend Firefox to all my friends - now it blows up in my face when they can't use other services I also recommend. I have been using Firefox since before it was called Firefox, and won't likely change because of this. But it's the first time I've had a problem I really can't solve, even with a difficult fix. There just doesn't seem to *be* a fix. I'm wondering if this is because of IonMonkey in FF18.
I have the same issue. My mouse clicks do not register any response. Use Windows 7 and Firefox v18. Have no problem in Explorer.
Okay, so I've done a lot more testing, and still - nothing! Absolutely nothing works, or makes any difference at all. I have completely removed Firefox, all it's leftover folders and profiles, and started from scratch with no imports or any data. On a fully fresh FF 18, iCloud.com still does NOT work. On a fully fresh FF 19 Beta 1, it does NOT work. On a fully fresh FF 17.01, it DOES work.
Downgrading to 17 is the only way I've been able to make any progress whatsoever. This is not a reasonable solution for me, or any of my "clients" whose computers are set to auto-update, as having the browser update from 17 to 18 would break it again.
The strangest part is that iCloud.com does work on my iMac (in Windows 7 64; OS X untested thus far) that has upgraded to FF 18. Again, though, not a satisfactory answer or solution because it is not my primary computer. I could really use some more feedback from anyone and everyone on this. So far, my only possible explanation is that it's some sort of hardware configuration that is tripping up Firefox. For example, my laptop (primary) is Intel Integrated Craphics (yes, crap-hics) and my iMac is NVidia (or similar) dedicated graphics card. The iMac does have hardware acceleration on - that option makes no difference on my laptop though except for the addition of UI graphics issues on Win 8.
It is possible that other elements are overlaying parts of the screen and make links un-clickable.
You can check which element has focus if you right-click a link and open the Inspector.
My FF at work was also automatically upgraded to v18 but icloud works on that computer. It's running Windows 7 64-bit. In terms of add-ons, both machines are running pretty much the same add-ons, so it shouldn't be that. Hope someone can find a fix/workaround soon. I hate using IE!
This theory of overlapping elements should also be more consistent (or less?) - basically it only occurs on my one laptop and none of my other 3 computers. They are Windows 7 64+32, OS X M. Lion, and even Ubuntu. It works on all them in Firefox 18 - except my Windows 8-64 laptop. Seems like that's the answer, but everyone else in this thread is running 7-64, so that can't be it. I've also done an absolute, complete, and highly thorough removal of all things Firefox, with a fresh install. None of those worked, except the previously mentioned downgrade to Firefox v17.
I am totally at my wit's end on how to fix this. I've tweeted @mozillafirefox but of course no answer yet. Maybe I shall bug them more. Get it...bug? (/claptrapvoice)
Look thru the Windows 8 Bugs at Mozilla to see if you can find a related Bug report.
If you can't find a related Bug, you can file a Bug report with Bugzilla.
Since you seem to have it narrowed down to an issue with Firefox in Windows 8, make sure that you make that the "prime suspect"
There are issues with 1.2.x versions of MooTools that aren't not compatible with current Firefox releases as a possible cause, but other script libraries may have similar issues.