It’s Friday again, meaning Mac developers world-wide should report at least a bug to Apple. By the time I’m done writing this entry, it will be Saturday, but I swear I started typing before!

In any case, before we get on to the actual bug, I wanted to remind everyone of something very important: report yourself the other RABF! Indeed, the more people report a specific bug, the more likely it is to be checked rapidly by the people at Apple. This is why the del.icio.us tag is so important for this to work – if everyone adds their RABF there, it will be a cinch for everyone to cross-report all the bugs.

With that said, on with the bug.

Continue reading »

 

I know it’s technically Saturday on the East Coast, but we’re close enough to call it Report-an-Apple-Bug-Friday. Today’s bug is particularly harmless but still annoying. Everything that can improve the Mac OS X user experience is a good thing, so even if this issue is only cosmetic, it’s still worth reporting it.

In addition, I will try to adopt Apple’s guidelines for bug reports, which go along the lines of Summary, Steps to Reproduce, Expected Results, Actual Results, Regression and Notes. Those subdivisions are a good idea for both the person who submits the report and for the person who will read the report, as they will encourage a more complete and structured exercise on both ends which will ultimately lead to faster bug fixing.

You can find more Report-an-Apple-Bug-Fridays by checking out the new del.icio.us tag applebugfriday.

One last note before the report – I won’t be posting them on the main content section anymore, since they could be lengthy. Read on!

Continue reading »

© 2011 /dev/klog Suffusion theme by Sayontan Sinha