為了改善您的使用體驗，本網站正在進行維護，部分功能暫時無法使用。若本站的文件無法解決您的問題，想要向社群發問的話，請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問，我們的社群成員將很快會回覆您的疑問。

Avatar for Username

搜尋 Mozilla 技術支援網站

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

了解更多

此討論串已被封存。 如果您有需要幫助，請新增一個新問題

Google Sheets Line break Bug in Firefox

Sablotin
Sablotin
more options

Hi,

I want to share a bug occurring in Google sheet using Firefox (uptodate, virgin profile).

The bug appeared few weeks ago here (https://productforums.google.com/forum/#!topic/docs/KlBdLukjw5s) and here (https://productforums.google.com/forum/#!topic/docs/A1MxM2-Bzjc). I summarize it here (https://productforums.google.com/d/msg/docs/8iZEqno94-4/-nX4UddalFQJ).

Using backspace within a cell then exiting the cell add a line break in the cell.

It could be considered as a pure google bug but it only happens in Firefox, in Chrome everything is normal.

I know it's somewhat a story of the chicken or the egg but maybe Firefox specialists could help understanding the bug.

Thanks in advance.

Hi, I want to share a bug occurring in Google sheet using Firefox (uptodate, virgin profile). The bug appeared few weeks ago here (https://productforums.google.com/forum/#!topic/docs/KlBdLukjw5s) and here (https://productforums.google.com/forum/#!topic/docs/A1MxM2-Bzjc). I summarize it here (https://productforums.google.com/d/msg/docs/8iZEqno94-4/-nX4UddalFQJ). Using backspace within a cell then exiting the cell add a line break in the cell. It could be considered as a pure google bug but it only happens in Firefox, in Chrome everything is normal. I know it's somewhat a story of the chicken or the egg but maybe Firefox specialists could help understanding the bug. Thanks in advance.
附加的畫面擷圖

由 Sablotin 於 修改

被選擇的解決方法

It sounds like Google is aware of the issue. There's not really anything we can do at this point. If Chrome developers need input from Firefox devs, they know where to find them. :)

從原來的回覆中察看解決方案 👍 0

所有回覆 (1)

Mark Schmidt
Mark Schmidt
more options

選擇的解決方法

It sounds like Google is aware of the issue. There's not really anything we can do at this point. If Chrome developers need input from Firefox devs, they know where to find them. :)