1583033 - Grammarly Extension doesn't recognize that it has been already signed in.

Status: RESOLVED INCOMPLETE

(WebExtensions :: Developer Outreach, defect, P5)

Description

[Pranav bhattarai]

Attachment: Screencast from 09-22-2019 03:59:22 PM.webm

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

Distro: Ubuntu 18.04.3 (Also happens in Windows 10 Pro)

Well, I see this every time, buggy Firefox nature I guess. But this is how it goes:

1. Install Grammarly extension

2. Try to log-in

3. U logged in but u are not logged in "extension section"

4. Wait for some hours, maybe restart Firefox, even OS, etc. After a while, you have logged in the extension section as if nothing has ever happened.

Question: Do the users have to get used to with this unusual behavior?

Actual results:

As a proof, a screencast video has been uploaded.

Expected results:

<>

Comment 1

[Simona Badau, Desktop QA]

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

I could not reproduce this issue on the latest Nightly 71.0a1.
Pranav, can you check if grammarly is listed with the right credential in the saved logins section? (Open menu-> Privacy and Security -> Logins and Passwords -> Saved Logins)

Comment 2

[Pranav bhattarai]

(In reply to Simona Badau from comment #1)

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

I could not reproduce this issue on the latest Nightly 71.0a1.
Pranav, can you check if grammarly is listed with the right credential in the saved logins section? (Open menu-> Privacy and Security -> Logins and Passwords -> Saved Logins)

Yes, Grammarly username and its password are saved.

Comment 3

[Alex Cornestean]

Hello,

I could not fully reproduce the issue based on the provided STR on the latest Nightly (71.0a1/20190930215436), Beta (70.0b10/20190926005616) and Release (69.0.1/20190917135527) under Windows 10 Pro 64-bit and MacOS High Sierra 10.13.6.

I have installed the extension and logged in, however, even after multiple hours and several browser and computer restarts, I still appear as logged out in the extension section from the toolbar, which is an issue in itself. As such, I will mark the issue as New and hopefully we will get some help from the developers in solving the problem.