Hacker News new | ask | show | jobs
by jgunsch 4090 days ago
I'm pretty sure this is https://code.google.com/p/chromium/issues/detail?id=464270, which was fixed by https://codereview.chromium.org/1007323003.
1 comments
jlblatt 4090 days ago
Wow, that's an even better guess than the other (not mine) I posted: https://news.ycombinator.com/item?id=9326350
link
jgunsch 4090 days ago
It's not just a guess, I broke it and I fixed it :)

Can I ask why you took the approach of making a Github repo to post this rather than filing a Chromium bug?

link
jlblatt 4090 days ago
I did file a Chromium bug last week, #472347. I filed under security (as I was unsure) so it's not public, but it was pretty much immediately marked as 'Won't Fix'. Hence the repo ;)
link
reitanqild 4089 days ago
Now this is interesting, especially the lack of a reply.
link
jlblatt 4089 days ago
The dev reached out to me privately, I wouldn't infer anything based on the responses here.
link
reitanqild 4089 days ago
Good to hear! Thanks for updating me.
link
omaranto 4089 days ago
I wouldn't call marking the bug as WONTFIX a "lack of reply".
link
reitanqild 4089 days ago
I see, I wasn't clear.

I talked about the lack of reply to the comment where this was pointed out.

Just asking why he didn't it and then leaving the conversation possibly means he either didn't wait for the answer or was bothered with it?

link