Hacker News new | ask | show | jobs
by jlblatt 4095 days ago
Wow, that's an even better guess than the other (not mine) I posted: https://news.ycombinator.com/item?id=9326350
1 comments
jgunsch 4095 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 4095 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 4095 days ago
Now this is interesting, especially the lack of a reply.
link
jlblatt 4095 days ago
The dev reached out to me privately, I wouldn't infer anything based on the responses here.
link
reitanqild 4095 days ago
Good to hear! Thanks for updating me.
link
omaranto 4095 days ago
I wouldn't call marking the bug as WONTFIX a "lack of reply".
link
reitanqild 4095 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
jgunsch 4095 days ago
Sorry, last night HN didn't show me a "reply" button on the thread, so I thought maybe it tapped out at a depth of four? I'm not dodging :) [edit: does HN have account score thresholds at which different features get enabled?]

I don't have security-bugs access, but I explained offline to the OP that "Won't Fix" covers a lot of cases, including "already fixed" / "duplicate", not simply "your bug report is being ignored".

OP also sent me some more information about the BrowserStack setup, and it looks like both the M42 and M43 builds that OP was testing against are nearly a month old and before the fix (merged to M42 late in beta phase, M43's still in dev/canary stage).

link