搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

Learn More

Pressing enter in multiline editor creates a space

  • 3 个回答
  • 2 人有此问题
  • 5 次查看
  • 最后回复者为 tgp1994

more options

Whenever I'm editing a multiline textbox (for example, here), pressing the enter button only appears to create a space in the editor, as if I had pressed the spacebar. If I close the editor and l look at the webpage, my new line shows up just fine. If I open up the editor again, any previously entered newlines show up as well, but subsequent ones will have the same result as before.

I am using an Incredible 2, with Virtuous Affinity as my rom. Other text apps (such as Gmail) work just fine.

Whenever I'm editing a multiline textbox (for example, here), pressing the enter button only appears to create a space in the editor, as if I had pressed the spacebar. If I close the editor and l look at the webpage, my new line shows up just fine. If I open up the editor again, any previously entered newlines show up as well, but subsequent ones will have the same result as before. I am using an Incredible 2, with Virtuous Affinity as my rom. Other text apps (such as Gmail) work just fine.

所有回复 (3)

more options

hi, I'm sorry you are having this problem with Firefox mobile v 10. I believe it is fixed in Firefox beta, so you might try that version, it is available in google play for android 2.2 phones.

thanks, Michelle

more options

It seems like the issue was not fixed in the beta. I am replying right now from FF 14. Besides the new line glitch, it seems like a regression has been introduced where the cursor constantly jumps to the beginning of the editor. I hope both of these bugs are fixed before the new version is given the green light!

Edit: I would like to be more specific about where this bug occurs; when I hold my phone in portrait mode, the website's editor works correctly. However, in landscape mode, using android's editor, that is where these two bugs occur.

由tgp1994于修改

more options

Any word on this being fixed? The issue is still present in the latest update, 16.0.2.