Hello henr!

I would recommend trying to uninstall then reinstall the Office 365 applications to see if that would solve your problems. If this does not help solve your problem, I would check to make sure it isn't an issue with your keyboard or the Firefox browser in general. You could also attempt to uninstall and reinstall Firefox.

If you need help uninstalling an add-on, you can view these articles:

• Disable or remove Add-ons

• Remove a toolbar that has taken over your Firefox search or home page

Hoped this helps!

Hi henr354a, could you check this:

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk.

(2) In the search box above the list, type or paste hack and pause while the list is filtered

(3) Check the dom.keyboardevent.keypress.hack.use_legacy_keycode_and_charcode preference -- Firefox 66.0.1 should have updated the value of this preference to

powerpoint.officeapps.live.com

Question: Is that the address where you have problems with PowerPoint online, or is it on a different domain?

Possible Workaround: The developers are building up this list to cover more sites. This is the list from yesterday, and it may expand:

*.collabserv.com,*.gov.online.office365.us,*.officeapps-df.live.com,*.officeapps.live.com,*.online.office.de,*.partner.officewebapps.cn,*.scniris.com

In order to test this out now:

(A) Select and copy the above list

(B) Double-click the dom.keyboardevent.keypress.hack.use_legacy_keycode_and_charcode preference to display a dialog where you can modify the preference value, clear the existing list, paste the new list, and click OK.

You need to reload the Office365 page before that would take effect, or open it in a new tab for testing. Any difference?

Request: If there are more Office365 sites that need a fix, please let us know the addresses. Thanks.

Hey. Thank you for your answers and solutions. I save them for later use. Thursday morning (Danish time), an update came to version 66.0.2, which contained a bug fix on the problem so that it was resolved.