3 ms·

He gets it.

masklinn 8y ago
They get nothing whatsoever. "Getting it" would at the very least mean checking the open bug trackers for existing issues, which there are, in all three (closed WONTFIX for Firefox and never even triaged for Webkit, Chromium's activity doesn't seem to go beyond triaging — all the issue having been created circa 2014~2015). "Getting it" is not creating worthless busywork for maintainers by spamming their bug trackers with pointless issues — unless you're reporting to the black hole that is Apple's RADAR — it might be actually deciding to take on the issue, getting a hold of the relevant stakeholders and asking if and what it would take for this to be merged if you implemented it, and being ready to be told "no" and "nothing because it won't be".
- TheRealPomax 8y ago
  No, I really do get it. Searching for a previous bug is part of filing, and you're talking about bugs that were filed three or even four years ago - so back when none of the current browsers were anything remotely like what they are today. As such, you (and others) should refile them going "these were marked wontfix 3~4 years ago but the spec and adoption has changed since then, please reconsider implementing this". I lost track of how many specs had to go through that. This is not "busywork for maintainers", that is how updating specs work. You WONTFIX a spec when it's too early, and then people can refile once the spec's been reworked, made usable, etc. If your project is the size of a browser, the number of issues you immediately close rivals or even eclipses the number of issues you actually work on - it's why you have weekly/daily triage sessions to go "what's now in our bin since last triage? dupe dupe wontfix dupe assign request-for-clarification wontfix, done let's get to work" I work for one of these companies, pretty sure I have at least a decent idea what I'm talking about. We WONTFIX specs that are too drafty, and then one or even more years later, you refile an implementation issue because the world has changed, and what was WONTFIX in the past, is now worth doing.

He gets it.

They get nothing whatsoever. "Getting it" would at the very least mean checking the open bug trackers for existing issues, which there are, in all three (closed WONTFIX for Firefox and never even triaged for Webkit, Chromium's activity doesn't seem to go beyond triaging — all the issue having been created circa 2014~2015). "Getting it" is not creating worthless busywork for maintainers by spamming their bug trackers with pointless issues — unless you're reporting to the black hole that is Apple's RADAR — it might be actually deciding to take on the issue, getting a hold of the relevant stakeholders and asking if and what it would take for this to be merged if you implemented it, and being ready to be told "no" and "nothing because it won't be".

TheRealPomax 8y ago
No, I really do get it. Searching for a previous bug is part of filing, and you're talking about bugs that were filed three or even four years ago - so back when none of the current browsers were anything remotely like what they are today. As such, you (and others) should refile them going "these were marked wontfix 3~4 years ago but the spec and adoption has changed since then, please reconsider implementing this". I lost track of how many specs had to go through that. This is not "busywork for maintainers", that is how updating specs work. You WONTFIX a spec when it's too early, and then people can refile once the spec's been reworked, made usable, etc. If your project is the size of a browser, the number of issues you immediately close rivals or even eclipses the number of issues you actually work on - it's why you have weekly/daily triage sessions to go "what's now in our bin since last triage? dupe dupe wontfix dupe assign request-for-clarification wontfix, done let's get to work" I work for one of these companies, pretty sure I have at least a decent idea what I'm talking about. We WONTFIX specs that are too drafty, and then one or even more years later, you refile an implementation issue because the world has changed, and what was WONTFIX in the past, is now worth doing.