3 ms·

Release schedules &c. aside, they have no argument if they're complaining about the Safari team's "communication". The diligence from the Safari team in respond

• lapcat 4y ago
  > Release schedules &c. aside, they have no argument if they're complaining about the Safari team's "communication". You can't put that aside, because it's the entire point! "The bug is fixed in the git repository, but we refuse to tell you if or when the fix will appear in Safari" is communication, but it's not the kind of communication needed for web developers. > The diligence from the Safari team in responding to those bug reports is not something I've seen from other browsers vendors. I have to disagree there.
  • lucideer 4y ago
    > You can't put that aside, because it's the entire point! Sorry I didn't mean to imply it wasn't relevant, merely that I wanted to address one small sub-point of your comment. > is communication, but it's not the kind of communication needed for web developers. That's fair, but it's relative: a quick response with a commitment of work (if not of timelines) & active dialogue on debugging efforts (due to the complete lack of effort on the part of the reporter) is a LOT better than no commitment or response, or a "please provide more info" / "WONTFIX" / CNR. Which is much more common. Particularly given I think a "please provide more info" would've been a perfectly reasonable response to the first report.