131–137 of 137 posts
Earlier quoted context omitted.
Yeah, that's not great, but the commenter in #12 is a senior engineer on devtools, so at least the right person saw it in the end.
looking at that ticket, the response from google is catastrophic . the guy or gal handling the ticket has no idea about web browsers. the reporter shows up with a complete reproducer and the best google manages is throw clueless screenshots (for a brief fully textual error message no less!) at them? they've already done a bunch of your work for free. get your ass off the heap of money, ffs! edit: oh, and i lower my h…
I would imagine that the chromium teams probably gets a lot of tickets. That means they need a lot of bodies to triage them. It's not like any Sr. Dev ist going to be jumping at that job.
Earlier quoted context omitted.
well thanks for doing your best to ensure they stop engaging on HN, i guess...
Tell me a better way to get Google to fix things, I'm all ears. Complaining in social media, bugging people you know inside the walls and calling them out here works
Earlier quoted context omitted.
looking at that ticket, the response from google is catastrophic . the guy or gal handling the ticket has no idea about web browsers. the reporter shows up with a complete reproducer and the best google manages is throw clueless screenshots (for a brief fully textual error message no less!) at them? they've already done a bunch of your work for free. get your ass off the heap of money, ffs! edit: oh, and i lower my h…
To be fair, the screenshot does provide additional info, like the fact that they are using file://.. It's often better to include more in a screenshot than less. I would imagine that the chromium teams probably gets a lot of tickets. That means they need a lot of bodies to triage them. It's not like any Sr. Dev ist going to be jumping at that job.
Earlier quoted context omitted.
It's pretty rare to use in user-code. It might be well used in libraries, but I guess the standard developer experience is using libraries not writing them.
Of course it’s rare because it’s unreliable and buggy as shit across browsers atm (tho a lot better than it was). So... somewhat self-fulfilling
I can echo his experience reporting browser bugs and provide my own reviews: Firefox - By far the best. Quick response, usually from engineers. If it's important the fix will be quick. Edge - No reply for months / years. When I've gotten replies back it's been to ask me to try with the current version. When I do and the bug still exists it goes back at the bottom of the queue it seems. Chrome - Somewhat of a mixed ba…
Did you report the Safari bug to Apple or to WebKit.org? I've had good luck getting responses and fixes from the webkit guys
Earlier quoted context omitted.
product-security@apple.com is the real one these days. Of course, this gets me thinking, what kind of super powers do these addresses have that allows people to send potentially malicious things there to be disassembled and analyzed? I suspect they are quarantined in some way, but it would be interesting to hear from the ops sec crowd how this gets handled.
Yes – I even got a nice email from someone apologizing about that and explaining that they were trying to get the security@apple.com people to at least forward messages when I did a full disclosure release after not receiving a response.