Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

calendar.google.com - clicking to edit event time selects time instead of inserting edit cursor #110760

Open
cpeterso opened this issue Sep 13, 2022 — with webcompat-app · 2 comments
Assignees
Labels
browser-firefox diagnosis-priority-p2 engine-gecko The browser uses the Gecko rendering engine priority-normal severity-important A non-core broken piece of functionality, not behaving the way you would expect.

Comments

@cpeterso
Copy link

URL: https://calendar.google.com

Browser / Version: Firefox 106.0
Operating System: Windows 10
Tested Another Browser: Yes Chrome

Problem type: Something else
Description: Clicking Google Calendar event's time selects time instead of inserting edit cursor in Firefox
Steps to Reproduce:

Steps to reproduce:

  1. Using Firefox, log into Google Calendar: https://calendar.google.com/
  2. Click an event to open its summary popup.
  3. Click the popup's "Edit event" button.
  4. Single click the event detail page's start or end time, such as 12:00pm. The event time will be selected in Firefox and Chrome on Windows and macOS and in Safari on macOS.
  5. Single click the event time again to insert an edit cursor.

Expected result:

An edit cursor should be inserted in event time so you can type or select individual digits. This is want happens in Chrome on Windows and macOS and in Safari on macOS.

Actual result:

In Firefox, the event time is still fully selected and no edit cursor is inserted. I can reproduce this behavior in the Firefox Nightly 106 (Windows and macOS) and ESR 91.13.0esr, so this is not a (recent?) Firefox regression.

View the screenshot Screenshot
Browser Configuration
  • None

From webcompat.com with ❤️

@webcompat-bot webcompat-bot added this to the needstriage milestone Sep 13, 2022
@webcompat-bot webcompat-bot added browser-firefox engine-gecko The browser uses the Gecko rendering engine priority-critical labels Sep 13, 2022
@cpeterso cpeterso changed the title calendar.google.com - see bug description calendar.google.com - clicking to edit event time selects time instead of inserting edit cursor Sep 13, 2022
@softvision-raul-bucata softvision-raul-bucata added severity-important A non-core broken piece of functionality, not behaving the way you would expect. priority-normal and removed priority-critical labels Sep 14, 2022
@softvision-raul-bucata
Copy link

@cpeterso We appreciate your report. I was able to reproduce the issue:
calendar ff

Tested with:

Browser / Version: Firefox Release 104.0 (64-bit)/ Firefox Nightly 106.0a1 (2022-09-13) (64-bit) /Chrome Version Version 105.0.5195.102 (Official Build) (64-bit)
Operating System: Windows 10 PRO x64

Notes:

  1. Reproducible regardless of the status of ETP.
  2. Reproducible on the latest build of Firefox Nightly and Release.
  3. Works as expected using Chrome:
    calendar chr

Moving this to NeedsDiagnosis for further investigations.

[qa_37/2022]

@cpeterso
Copy link
Author

Single click the event detail page's start or end time, such as 12:00pm. The event time will be selected in Firefox and Chrome on Windows and macOS and in Safari on macOS.

I can still reproduce this bug in Firefox Nightly 116. Interestingly, Safari's behavior (now version 16.5) seems to be different now from what I described back in 2022: the first click to focus the event time field inserts an insertion point cursor instead of selecting the event time. The second click selects the time. This is the reverse of Chrome's behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
browser-firefox diagnosis-priority-p2 engine-gecko The browser uses the Gecko rendering engine priority-normal severity-important A non-core broken piece of functionality, not behaving the way you would expect.
Projects
None yet
Development

No branches or pull requests

5 participants