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

[Tracking] Chrome on windows 10 losing URL fragments #26

Open
andre-d opened this issue Jul 31, 2015 · 6 comments
Open

[Tracking] Chrome on windows 10 losing URL fragments #26

andre-d opened this issue Jul 31, 2015 · 6 comments
Labels

Comments

@andre-d
Copy link
Contributor

andre-d commented Jul 31, 2015

https://code.google.com/p/chromium/issues/detail?id=514162

@k3d3
Copy link
Contributor

k3d3 commented Nov 23, 2015

Looks like this was fixed upstream.

@k3d3 k3d3 closed this as completed Nov 23, 2015
@andre-d
Copy link
Contributor Author

andre-d commented Nov 23, 2015

As this is a tracking issue please leave this open until fixed in stable
chrome at which point the potential for this bug coming up again is
minimal. Beta is not soon enough to close an upstream tracking issue, a
comment or tag for "fixed upstream in beta" is better until fixed in stable.
On Nov 23, 2015 4:48 PM, "Keith M" [email protected] wrote:

Looks like this was fixed upstream.


Reply to this email directly or view it on GitHub
#26 (comment).

@ultramancool
Copy link
Contributor

I'd say it's good to close. it's off our plate and we don't need to give a
shit anymore.
On Nov 23, 2015 5:02 PM, "Andre d" [email protected] wrote:

As this is a tracking issue please leave this open until fixed in stable
chrome at which point the potential for this bug coming up again is
minimal. Beta is not soon enough to close an upstream tracking issue, a
comment or tag for "fixed upstream in beta" is better until fixed in
stable.
On Nov 23, 2015 4:48 PM, "Keith M" [email protected] wrote:

Looks like this was fixed upstream.


Reply to this email directly or view it on GitHub
#26 (comment).


Reply to this email directly or view it on GitHub
#26 (comment).

@k3d3 k3d3 reopened this Nov 23, 2015
@k3d3
Copy link
Contributor

k3d3 commented Nov 23, 2015

Reopened for now to keep some peace - I'll leave it to @andre-d to manage this issue and close it when appropriate.

@andre-d
Copy link
Contributor Author

andre-d commented Nov 23, 2015

This can be closed once Chrome 48 goes stable channel, currently dev channel

@ultramancool
Copy link
Contributor

Since @andre-d is primary on this, I'll leave this his way even though it seems annoying to me just to see it open all the time, but I'm not the one who has to look at it open on the default issue tracker screen... if only github had other states this wouldn't be annoying.

@ultramancool ultramancool reopened this Nov 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants