Firefox oddity

Ok, seems this a.t.timeout thing is stranger than I thought. Yesterday 0 caused no timeout. Today it means instant timeout??

I guess I should just get the source and figure out where the problem is, but I feel lazy. :)