1605018 - Intermittent issue in Google spreadsheet: moving out of a cell adds vertical space

Status: RESOLVED FIXED

(Web Compatibility :: Site Reports, defect, P3)

Description

[painful8th+github.com]

Attachment: thread-22089163-4960542147951573596.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0

Steps to reproduce:

I've been using Google Docs for a long time, with Firefox as my primary browser. In the last year (only) I've noticed intermittent issues when editing a (rather old) spreadsheet. Specifically, regardless if I'm typing in Greek or English, moving out of the cell (via enter, tab or cursor keys) adds vertical space to the cell. I'm attaching a picture of the issue. Again, the issue is not always reproducible.

I've also posted in the google forums in the hope I'll find someone to help. It seems two other firefox users have encountered the same behaviour.

Actual results:

Vertical space added to the cell contents.

Expected results:

Cell height should not have changed.

Comment 1

[painful8th+github.com]

Forgot to paste the google groups link: https://support.google.com/docs/thread/22089163?hl=en

Comment 2

[Simona Badau, Desktop QA]

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0

I can confirm that this issue is reproducible on the latest Nightly 73.0a1 on Windows 10.
Unfortunately, because the issue is intermittent I could not determine the regression range yet, and neither reliable steps to reproduce it (I logged into my google account, created a new spreadsheet, added data and moved between the cells using the tab, enter and arrow keys).
So far, I managed to reproduce it also on Firefox 71 and on Firefox 72 beta 10 but, I could not reproduce it on Firefox 68.3.0 esr.
When time permits I will investigate more.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug is a regression, but please revert this change in case of error.

Comment 4

[Liz Henry (:lizzard) (relman/hg->git project)]

Too late for a fix in 72, but we could take a patch for 73 or 74.

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

The priority flag is not set for this bug.
:marcia, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 6

[painful8th+github.com]

Adding some information as found in https://support.google.com/docs/thread/18235069?msgid=23142057 this might be related to auto-complete.

Comment 7

[Marcia Knous [:marcia]]

The discussion in https://support.mozilla.org/en-US/questions/1272896 is interesting, and leads to a a similar bug, Bug 1192656 referenced in the mozilla support thread - is this the same issue as what is described in that bug?

Comment 8

[painful8th+github.com]

Yes, it does seem to be the same issue. It has been closed 4 years ago, but it seems that the issue persists. Specifically it is easily reproducible, even on a brand new calc sheet, by entering some text, deleting it with backspace and reentering some more.

I also read the last comment by :hallvors. While I do somewhat agree with this policy (as someone affiliated with coding), it reflects badly for FF. "Others browsers do not have this issue, FF does". Also, I use Google calc extensively and the issue is becoming troublesome, to say the least.

Bottomline: the issue outlined in this thread could be declared a duplicate of bug 1192656. However, I'd be grateful if someone could rock the boat at Google, or wherever else is needed, in the hope that whatever did not happen 4 years ago, will possibly happen now.

Comment 9

[Ryan VanderMeulen [:RyanVM]]

I see this all the time too. Mike, can we try reaching out to Google?

Comment 11

[Mike Taylor [:miketaylr]]

Masayuki found the cause here: https://bugzilla.mozilla.org/show_bug.cgi?id=1609918#c7

Comment 13

[Mike Taylor [:miketaylr]]

I've emailed the gsuite team on our internal list.

Comment 14

[Mike Taylor [:miketaylr]]

(update: the team has filed an internal bug, and last we heard were looking for an owner to take a look)

Comment 15

[Pascal Chevrel:pascalc]

Mike, did you get an update from the gsuite team?

Comment 16

[Mike Taylor [:miketaylr]]

Nothing since they told us an internal bug was filed. I'll ask for an update.

Comment 17

[Pascal Chevrel:pascalc]

Marking as fix-optional for 74 since this is webcompat, to remove it from our regression triage weekly queue.

Comment 18

[Adam Stevenson [:adamopenweb]]

Following up on this report. I've seen this issue many times before but I'm not able to reproduce right now in testing. Can someone confirm if it still reproduces for them please? (maybe Simona?)

Comment 19

[Simona Badau, Desktop QA]

(In reply to Adam Stevenson [:adamopenweb] from comment #18)

Following up on this report. I've seen this issue many times before but I'm not able to reproduce right now in testing. Can someone confirm if it still reproduces for them please? (maybe Simona?)

I can't reproduce it on my end. Tested on Windows 10x64 using the latest Nightly 76.0a1.

Comment 20

[Mike Taylor [:miketaylr]]

Ryan, can you repro anymore? Possible fixed by Google.

Comment 21

[Michail Pappas]

For the record, I can not reproduce this issue anymore.

Comment 22

[Ryan VanderMeulen [:RyanVM]]

(In reply to Mike Taylor [:miketaylr] from comment #20)

Ryan, can you repro anymore? Possible fixed by Google.

Haven't had much occasion to test recently. Feel free to resolve the bug if nobody else can. We can always re-open if it comes back.

Comment 23

[u655357]

Michail Pappas
For the record, I can not reproduce this issue anymore.

I too @ Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0

Comment 24

[Mike Taylor [:miketaylr]]

Cool, thanks everyone. And thanks Google, seems like they fixed it.