![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
Firefox backspace doesn't work in new iCloud Calendar on the web...
Hi all,
Apple has revised/updated their iCloud web portal. The backspace key no longer registers in the iCloud Calendar app on the web. This is specific to Firefox on Windows - I've tried other web browsers to access iCloud web portal and Chrome's backspace key registers so its not an Apple iCloud problem, just Firefox. Is there a setting or do I have to wait for an update?
Thanks in advance.
Svi odgovori (19)
Does it still happen in Troubleshoot Mode?
Yes, it happens in Troubleshoot Mode too.
Does it still happen in a new profile? An easy way to test a new profile is to install Developer Edition and see if it happens there or refresh your existing profile.
Yes it happens in Troubleshoot Mode as well.
My iCloud Calendar works on Safari on my iMac 24 but not with FireFox on iMac or my Windows laptop.
We know this problem is specific to Firefox but we now know it's not just Firefox PC but MacOS as well.
Is there a proper tech support to report this problem?
You can test older versions with mozregression to help identify the problem.
I'm having the same issue. I have to log into Safari to get the backspace/delete key to work in iCloud.com. Super frustrating as Firefox is my default browser.
Can someone elevate this issue to the developers please?
Does Firefox employees even monitor these pages? If so, they should know this is a real problem for a lot of people.
How does one actually report a bug to actual Mozilla? It's not my configuration but all Firefox on all my computers. Its quite annoying without backspace - you never knew until you don't have it.
Here's the thread on the Apple Support site; https://discussions.apple.com/thread/255180069?login=true
Could this be interfering with the browser.backspace_action pref (0:B/F;1:PgUp/PgDn;2:Nothing) ?
You can create a new profile as a quick test to see if your current profile is causing the problem.
See "Creating a profile":
If the new profile works, you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.
I don't speak Developer and the suggestions about code and profiles are both lost on me. The supposed "fixes" sound like they call for major efforts by each User to correct an isolated (though colossally troublesome) glitch in the communication between Firefox and the new iCalendar.
Can a Developer at Mozilla please talk to a Developer at Apple/iCloud to figure out where and why the two programs have decided not to talk with each other? It's terribly unfair to make each one of your Users become a mini-Developer to fix this.
So Mozilla- what is the simple fix for those of us asking? Are you on this? It's a problem for many of us.
Apple updated it's iCloud calendar, which it did (I confirmed with an Apple representative), what does it take for Mozilla to make the necessary adjustments for this issue?
Are the changes inside Mozilla/Firefox, etc. causing this to get lost?
I think we are such a small minority of users here that we're not even on their radar of support. I wished there was some way of bringing up this problem with Mozilla?
Well, it seems as though Apple has solved the problem as they just changed their iCloud Calendar interface and the backspace key now works again. I am a little disappointed that there has been no official way to ask for help from Mozilla nor any replies from them since October.
Glad Apple rectified the situation.
Creating a new profile certainly didn't help and was a huge waste of time! (do not follow those solutions)
If you used the Profile Manager to create a new profile, then you should be able to return to the current/old profile at any time unlike with using refresh that moves the profile to the desktop.
But that wasn't the problem and didn't solve the issue. It was something that was coded in the site or how Firefox interpreted that code in the site. It has now been resolved by the site refresh and not by creating a new profile. I just wanted to save people a lot of my time trying that procedure and it didn't work until they changed something in the site now.
Testing in a new profile is an essential troubleshooting step that should not be discouraged. The easiest way is to install Developer Edition, see if it works. Done.