> On Mar 5, 2015, at 2:29 PM, Jens Alfke <j...@mooseyard.com> wrote: > > > I wouldn’t expect a response from Apple in ‘only’ a month, except perhaps to > notify you that it’s a duplicate. > > If they do fix the bug, you won’t get a notification until there’s a > developer release of the OS update so you can test the fix. And since this is > a pretty minor bug in the grand scheme of things, I wouldn’t expect a fix in > a dot-dot release. So I’d be guessing the earliest you might hear back about > a fix is around WWDC (June?) when there’s hypothetically a DP of 10.11. > > Until then you’ll need to work around it.
Okay, thanks. I guess I was expecting at least a “we’re looking into this” or “we won’t touch this” sort of reply. I think I can find a workaround for now. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
