搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

spacebar in AOL

more options

why is my space bar not working in AOL comment area?

why is my space bar not working in AOL comment area?

所有回覆 (7)

more options

Someone posted about a blog where typing a space doesn't work. I wonder if it's also an AOL property? You can check out that question here: https://support.mozilla.org/questions/1388408

more options

Same here. Also in the Wall Street Journal comments section.

more options

Problem does not go away in safe mode.

more options

twincaman said

Problem does not go away in safe mode.

Thank you for testing that. Apparently it started on Fox News chat on Sunday as well:

https://support.mozilla.org/questions/1388487

I assume the site changed something and didn't test Firefox compatibility. But someone still needs to come up with a solution or workaround.

Please do report it to WSJ. As a subscriber you probably have more ways to give feedback than random internet people.

more options

As I've been fooling around with it I've found that after typing a word the spacebar seems to work but the space disappears as soon as I begin typing the next word. If I then put the cursor back between the words, I can get the space and it sticks. After doing this for 9 or 10 words, it begins to work normally. When starting a new comment, it starts all over again. Very strange indeed.

more options

My Firefox started this Monday, 9/5/22 after an "upgrade". A shame such a basic function gets broken. And there are reports of this going back to April. I have the same issue on any comment site. Funny thing is, commenting here works fine. I do hope the "Coders" resolve this soon.

On thing I saw suggested that worked, kinda, was this. Type some gibberish characters, 4 or 5. Then go back behind those characters and Voila! The space bar works as intended. You can then delete the characters after typing your sentences.

more options

cstones2u said

My Firefox started this Monday, 9/5/22 after an "upgrade".

As far as I can tell, this is caused by a recent change in a comment system shared across the customers of this comment section service provider: https://www.openweb.com/