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.

Sign up for GitHub

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

Jump to bottom

Chrome 76 (upcoming release) doesn't work with Riot #9924

Closed
2 tasks done
turt2live opened this issue May 31, 2019 · 5 comments
Closed
2 tasks done

Chrome 76 (upcoming release) doesn't work with Riot #9924

turt2live opened this issue May 31, 2019 · 5 comments
Assignees
@jryans
Labels
P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@turt2live
Copy link
Member

turt2live commented May 31, 2019 •
edited by jryans
Loading

I'm labelling this as p1 major because our user base uses Chrome and the next Chrome release is going to suck for them.
@turt2live turt2live added T-Defect P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround labels May 31, 2019
@turt2live turt2live mentioned this issue May 31, 2019
Closed
@lampholder
Copy link
Member

This will become stable Chrome on July 30

@turt2live
Copy link
Member Author

and because of that release day, we'll review this sometime between now and then rather than immediately. We're hoping that Chrome considers the issues bugs and fixes them so we don't have to.

@jryans jryans changed the title Chrome Canary (next release) doesn't work with Riot Chrome 76 doesn't work with Riot Jun 4, 2019
@jryans jryans changed the title Chrome 76 doesn't work with Riot Chrome 76 (upcoming release) doesn't work with Riot Jun 4, 2019
@turt2live turt2live mentioned this issue Jun 10, 2019
Closed
@k80w k80w mentioned this issue Jun 10, 2019
Closed
@bwindels
Copy link
Contributor

bwindels commented Jul 3, 2019

Both linked bugs are closed, does that mean this can be closed as well?

@jryans
Copy link
Collaborator

jryans commented Jul 3, 2019

Well, it's a bit confusing, as I believe both bugs were closed "in favour of" this meta-bug even before the problems had been investigated, which was a bit surprising... Anyway, their closed state is less useful than usual.

In any case, I'll retest in Canary and see what happens.

@jryans jryans self-assigned this Jul 3, 2019
@jryans
Copy link
Collaborator

jryans commented Jul 3, 2019

All listed problems appear to be working correctly with Chrome Canary 77, so it appears everything is fixed here.

@jryans jryans closed this as completed Jul 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jryans jryans

Labels
P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@bwindels @jryans @turt2live @lampholder