Just today I was writing some code and wondering why my accessKey properties didn’t seem to be working in Mozilla. Turns out it was bug #959 which was just fixed. Of course, that doesn’t explain why my code wasn’t working in IE, heheh. (Random thought – how hard would it be to create links to bugzilla bugs that would automatically cross out when the bugs were fixed? hmm, the easiest way I can think of is with a little spider that’ll automatically scrape for links and check the status. I suppose one could write a fancy schmancy reference table in conjunction w/ a big cms, or use some sort of wire protocol to do on-the-fly/caching queries and rendering… I wonder if xlink arcs would be able to do this?)
Oh, there’s a nice Mozilla Keyboard Planning FAQ and Cross Reference document that was put up in early 2001 which sure beats the hell out of looking through the source code for eht key codes, which I had to do when I was mucking around the summer before. (does that make me hard core, or just really dumb?)