4 ms·
I don't think the person who brought it up was aware the issue was associated with the Linux/X11 user agent, unfortunately, so couldn't provide support with the
by jplayer01 8y ago
I don't think the person who brought it up was aware the issue was associated with the Linux/X11 user agent, unfortunately, so couldn't provide support with the right information to actually reproduce the issue in a useful way. Still, it shouldn't have been an issue for this long, and who knows when they'll actually get around to fixing it. I don't think they're in a hurry to help Linux or Android users.
- windexh8er 8y agoI would disagree. It is not the end users job to hand an organization like Apple the issue on a silver platter. The user presented a 100% reliable reproduction of the issue to Apple Support. Apple ignored it and defending them by saying it wasn't presented in a "useful way" is, in my opinion, diminishing both what was brought to Apple in a relatively complete way and Apple failing to simply acknowledge or understand there is a problem. I agree it likely won't be fixed anytime soon. It probably impacts single digit (or less) percentages of their users.
- jplayer01 8y agoDid he once mention what kind of OS, phone or device he was using? There's like no actionable information there.
- windexh8er 8y agoIndirectly, yes - they did. All of this information can be deduced from the browser in Browserling that was referenced as working example to reproduce the error. There are many actionable data that can be deduced given what was provided to Apple. While there are many others, the site below [0] could have been used from the Browserline instance in question to deduce header information which would have included the OS as you've requested. Someone in Apple Support could likely figure this out given that information and ability to reproduce. [0] https://httpbin.org/#/Request_inspection/get_headers https://httpbin.org/#/Request_inspection/get_headers
- deleted 8y ago[deleted]