As someone who has filed many radar bugs in the past, I don't think it's a literal claim to Apple never fixing any bugs whatsoever.

It's that they seem to be very arbitrary about which bugs they fix, they don't seem to fix a lot of what's reported, and the entire system is closed and black-boxed.

Here's the process in most sane places:

- You file the bug in a place that's visible to the public. You can link other people to it, for example. "Oh yeah, that's a bug, here's the bug report [link]"

- Developers responsible discuss the bug in said bug tracking software.

- Someone eventually marks some kind of disposition on the bug "can't replicate", "won't fix", "fixed", etc. Bonus points if they can give some rough estimate on fix availability "should be available in next week's build", for example.

here's how the Apple process works:

- You file the bug in a private bug tracker. This bug report is only visible to you (and Apple), so you can't link it. When users report bugs in forums the only solution is "I filed it already, but I can't link to you, you should file it again". In fact Apple encourages the repeated filing of the same bugs as a "vote" mechanism.

- Apple never contacts you, or anyone else, about said bug unless they specifically need help tracking it down. This is rare.

- There is no word on the disposition of the bug in any case. If it's fixed, you don't hear about it. If they're passing on the bug, you don't hear about it. If it's not-really-a-bug, you don't hear about it. The only way for you to know if your bug got fixed is to download each new release and try to repro the bug for yourself.

So sure, Apple certainly does fix bugs, but the way they handle bug reports and resolution makes them one of the worst companies to work with from a bug reporting and triage perspective.

[edit] Not to mention that fairly major bugs go unfixed for a very long time. If you have a iOS7 device give this a go: go to Calendar (yes, that first-party built-in app), create a new event. Type in a long description - one that exceeds the size of the textbox. Your text now overflows without scrolling and just disappears off the edge of the control. Oops.

This bug existed all the way from iOS7 beta 1. Naturally, something this basic was reported constantly on the forums, with the requisite multi-page bitch-fest from devs. People filed bug reports on this, but as usual there was never any feedback from Apple. So beta 2 came along and it wasn't fixed, but people kept supposing they'd fix in the next one. Then the next one. Then the next one.

And here we are, iOS 7.0.2 and it's still not fixed.

Apple isn't exactly known for being very on top of their bug-fixing game.

This is the right way to get Apple to fix bugs: exaggerate and get it on HN. Worked like a charm for me[1].

[1] http://phoboslab.org/log/2012/07/what-the-fucking-fuck-apple

Yeah, I think the translation there is "The bugs I report always seem way higher priority to me than they do to Apple."

Yeah, I just checked that as well. Perhaps after a touch event occurs, Safari iterates across all DOM nodes with the same tag to see which DOM node's coordinates intersects with the touch's XY point?

This should be renamed to iOS7 Disaster! Oh and also this crashes on most modern browsers too...

Same goes for Chrome 29.0.1547.76

Safari 6.0.5, works without problems on my desktop, Safari 7.0 freezes on my notebook too.

Same,

OS X 10.7.5 (11G63) Safari 6.1 (7537.66)

Chrome (on iOS) does not use Nitro, it uses WebView.

Yeah. I get that it's a problem that iOS7 safari crashes with a lot of inputs, but that's an insanely-huge number of inputs. This is kind of an edge-case and you should probably avoid doing that in your web-pages. A hundred-ish inputs per-page is probably a better idea.

I haven’t noticed anything of the sort. For instance, my Instapaper and 1Password bookmarklets work fine in Mobile Safari.

A quick search query also doesn’t turn up anyone else having problems. What exactly isn’t working for you?