Perhaps they did use your page and perhaps it worked for them? Or perhaps your whiny tone made them disregard you as a serious witness, and so perhaps the problem is you. As other commenters point out you can't write clear instructions, what confidence should we have in your ability to write correct code?
I filed all the bug reports in a professional manner, without insults or swearing. I have a lot of respect for the engineers working at Apple, I just hate their company politics.
The blog post on the other hand was written in that manner to get public attention - which seems to have worked.
The code for the test case is about 20 lines of JavaScript. You don't have to trust me to write correct code, you can easily check it yourself.
The corporate overlords are not screening your bugs, the engineers are. Your mention that your bug got closed as a dup? And that the dup was closed as not being reproducible? It seems likely that either it wasn't really a dup or that the second bug didnt have steps that allowed it to be reproduced. In your case, I would think re submitting your as a new bug, referencing the other two, would probably bring some traction. Openradar is also an option for making your reports more public, and possibly getting more traction.
I believe you can also get public attention without resorting to such tactics. As much as I agree with your underlying position, I am sufficiently turned off by your tone and presentation that I, for example, would not go out of my way to ask anyone I might know at Apple what was up with the bug, or (of it were something I felt I could control) fix it myself. Your audience should not be people who will be riled up by vitriol: it should be other professional developers, and a larger internal-to-Apple community.
I wouldn't be surprised if other people at Apple now just feel insulted, and the people working on this problem likewise demoralized; all with the result that you are even /less/ likely to see a bug fixed in this project in a short period of time (and even if someone does "react" to this one, to be slightly more hostile and slightly less forgiving of your future bug reports, even of they are posed in a "professional manner", as they now "know better").
