Im sure that they have seen us. However, im not sure if it will get fixed in 10.5.10. If I remember it correctly, the first maintenance release of 10.0 was build about the same time as 10.0 was released. I guess due to they want it released before christmas and they have ha month of testing. (Dont blame me, this issue is so bad that they should do a 10.5.01 without full test scope…) But it also seems so common that they might have known the issue for a long period and has a fix for the december release.