I used that same link, and confirmed it fixed the 4-month-old problem here, almost two weeks ago (11/9).
Whatever the fix might be it's possible its implementation is either risky or the fix exposes other bug(s); these are my guesses why it might not have been implemented yet.
I agree with a recent post, it's disappointing to not hear/see the status of problems we've reported, but keep in mind that's not exactly the kind of dirty laundry they would want waving around in public.
My guess, too, is that they're too busy to keep a database of who reported what, and then email a bug status list; where I work, a full regression test is always performed after any fix is to be rolled out; who better to verify the fix than those who experienced/reported it?