On Mon, 12 Aug 2002, Jim Jagielski wrote: > >> The following patch allows this to be worked around using our > >> standard BrowserMatch envariable mechanism. It's against > >> 1.3, since that's the version with the most penetration at > > > the moment and where the problem is most visible.
likewise +1