Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Spell Check corrected word still retains the red underline #9324

Closed
srirambv opened this issue Jun 7, 2017 · 6 comments
Closed

Spell Check corrected word still retains the red underline #9324

srirambv opened this issue Jun 7, 2017 · 6 comments

Comments

@srirambv
Copy link
Collaborator

srirambv commented Jun 7, 2017

  • Did you search for similar issues before submitting this one?
    Yes

  • Describe the issue you encountered:
    Spell Check corrected word still retains the red underline

  • Platform (Win7, 8, 10? macOS? Linux distro?):
    All

  • Brave Version (revision SHA):
    Brave 0.16.4
    rev 15d8d36
    Muon 4.0.0

  • Steps to reproduce:

    1. Open about:styles
    2. Type in fead , ensure red under line is shown
    3. Right click, select correct text, still retains the red underline, is dismissed after mouse click
  • Actual result:
    Spell Check corrected word still retains the red underline

  • Expected result:
    Should dismiss the red underline after text is corrected

  • Will the steps above reproduce in a fresh profile? If not what other info can be added?
    Yes

  • Is this an issue in the currently released version?
    No

  • Can this issue be consistently reproduced?
    Yes

  • Extra QA steps:
    1.
    2.
    3.

  • Screenshot if needed:

  • Any related issues:
    Spell check not working with C59 #9102

@srirambv srirambv added this to the 0.17.x (Frozen, only critical adds from here) milestone Jun 7, 2017
@bbondy
Copy link
Member

bbondy commented Jun 12, 2017

@alexwykoff @srirambv could you compare against Chrome spell check? Is the issue also there?

@srirambv
Copy link
Collaborator Author

@bbondy Yes its the same behaviour on Chrome also

@darkdh
Copy link
Member

darkdh commented Jun 12, 2017

kapture 2017-06-12 at 11 37 39

@bbondy
Copy link
Member

bbondy commented Jun 13, 2017

I think we should probably sit on this until C60 and retest in both Chrome and Brave.

@bbondy bbondy removed this from the 0.17.x (Beta Channel) milestone Jun 13, 2017
@darkdh
Copy link
Member

darkdh commented Jun 13, 2017

Just verified Chrome 61.0.3128.0 has fixed this problem

@luixxiul luixxiul added this to the 0.19.x (Nightly Channel) milestone Jun 18, 2017
@luixxiul luixxiul removed this from the 0.19.x (Beta Channel) milestone Jul 18, 2017
@luixxiul
Copy link
Contributor

luixxiul commented Sep 7, 2017

Accoding to #9324 (comment) I'm going to close this issue, and adding it to the latest milestone to make sure this would be tested by QA. thanks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.