4 ms·

I'm pretty sure this is https://code.google.com/p/chromium/issues/detail?id=464270 https://code.google.com/p/chromium/issues/detail?id=464270, which was fixed b

by jgunsch 11y ago

I'm pretty sure this is https://code.google.com/p/chromium/issues/detail?id=464270 https://code.google.com/p/chromium/issues/detail?id=464270, which was fixed by https://codereview.chromium.org/1007323003 https://codereview.chromium.org/1007323003.

jlblatt 11y ago
Wow, that's an even better guess than the other (not mine) I posted: https://news.ycombinator.com/item?id=9326350 https://news.ycombinator.com/item?id=9326350
- jgunsch 11y 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?
  - jlblatt 11y 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 ;)
    - reitanqild 11y ago
      Now this is interesting, especially the lack of a reply.
      - omaranto 11y ago
        I wouldn't call marking the bug as WONTFIX a "lack of reply".
        reitanqild 11y 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?
        jgunsch 11y 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).
        jlblatt 11y ago
        TY, I'll update the readme.md when I get home tonight. And you are right, it was initially marked as "Won't Fix" because it was not immediately reproducible, but further research yielded it being discovered as an "already fixed" dupe. FYI it seems there is a minimum age (a minute or so) to a comment in order to reply. At least that was my experience last night.
        reitanqild 11y 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? Aha, the automatic flamewar limiter I guess. Happens to me as well. (clicking on the xx minutes ago link seems to help most of the time.) > 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". I don't know what I'd do if anyone reporting to me used wontfix for all those kind of cases. It doesn't exactly encourage bug reporting.
      - jlblatt 11y ago
        The dev reached out to me privately, I wouldn't infer anything based on the responses here.
        reitanqild 11y ago
        Good to hear! Thanks for updating me.

by jgunsch 11y ago

jlblatt 11y ago

Wow, that's an even better guess than the other (not mine) I posted: https://news.ycombinator.com/item?id=9326350 https://news.ycombinator.com/item?id=9326350

jgunsch 11y 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?
- jlblatt 11y 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 ;)
  - reitanqild 11y ago
    Now this is interesting, especially the lack of a reply.
    - omaranto 11y ago
      I wouldn't call marking the bug as WONTFIX a "lack of reply".
      - reitanqild 11y 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?
        jgunsch 11y 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).
        jlblatt 11y ago
        TY, I'll update the readme.md when I get home tonight. And you are right, it was initially marked as "Won't Fix" because it was not immediately reproducible, but further research yielded it being discovered as an "already fixed" dupe. FYI it seems there is a minimum age (a minute or so) to a comment in order to reply. At least that was my experience last night.
        reitanqild 11y 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? Aha, the automatic flamewar limiter I guess. Happens to me as well. (clicking on the xx minutes ago link seems to help most of the time.) > 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". I don't know what I'd do if anyone reporting to me used wontfix for all those kind of cases. It doesn't exactly encourage bug reporting.
    - jlblatt 11y ago
      The dev reached out to me privately, I wouldn't infer anything based on the responses here.
      - reitanqild 11y ago
        Good to hear! Thanks for updating me.