Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Google Sheets Line break Bug in Firefox

  • 1 ŋuɖoɖo
  • 6 masɔmasɔ sia le wosi
  • 1 view
  • Nuɖoɖo mlɔetɔ Mark Schmidt

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.
Screen ƒe photowo kpe ɖe eŋu

Sablotin trɔe

Ŋuɖoɖo si wotia

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. :)

Xle ŋuɖoɖo sia le goya me 👍 0

All Replies (1)

more options

Ɖɔɖɔɖo si wotia

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. :)