Avatar for Username

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

이 쓰레드는 보존되었습니다. 만약 도움이 필요하시면 새로운 질문을 올려주세요.

Google Sheets Line break Bug in Firefox

  • 1 답장
  • 6 이 문제를 만남
  • 17 보기
  • 최종 답변자: Mark Schmidt

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