Open Bug 1926087 Opened 5 days ago Updated 3 days ago

option-backspace deletes the space before a word in a google doc comment

Categories

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

Tracking

(Not tracked)

People

(Reporter: overholt, Unassigned)

References

(Depends on 1 open bug, )

Details

(Keywords: webcompat:platform-bug, webcompat:site-report)

User Story

platform:windows,mac,linux
impact:annoyance
configuration:general
affects:all
branch:release

STR

  1. make a comment in a Google doc (test doc with open comment access: https://docs.google.com/document/d/1aVt8D20lAnL3ZgDLQmN0KiwASpGI98rH8gi70Yi3Y1w/edit?tab=t.0)
  2. as you're typing the comment, try to delete the word you just typed by pressing option-<delete> (on a Mac; I haven't tested elsewhere) and then continue typing

Expected

  • can type the rest of your comment with the pre-existing space character remaining

Actual

  • space character is deleted so you end up withcontentlikethis

Note: this doesn't reproduce in Chrome.

This might be a dupe of bug 1925635.

Yup, looks like a dupe. The textfield in the google doc comment is a contenteditable div.

(Glob mentioned this in bug 1925606 comment 7, too. Given that you and glob both stumbled across this within 12 hours of each other, I wonder if Google changed something recently that made us trip over this more often in that google-docs scenario.)

(I can repro with overholt's provided STR, btw.)

Let's morph this into a webcompat site report, dependent on bug 1925635.

(Sort of a dupe of the other dependency -- gmail site-report bug 1925606 -- given that there's probably a single Google codebase that provides these contenteditable textfields under the hood, but also probably worth tracking the fact that multiple google properties are affected.)

Component: DOM: Editor → Site Reports
Depends on: 1925635
Product: Core → Web Compatibility
See Also: 1925635
Severity: -- → S4
User Story: (updated)
Priority: -- → P2

This turned out to have been partly-caused by the patches that landed in bug 1923251. Masayuki and I backed that out earlier today, which will probably make this no-longer-reproducible in tomorrow's nightly, hopefully.

You need to log in before you can comment on or make changes to this bug.