Re: [Zope-dev] 2.3.0 release badness

2001-01-29 Thread Martijn Faassen
[EMAIL PROTECTED] wrote: > I've just updated to 2.3.0 release using CVS. My CSS serving has > subsequently broken. The CSS serving worked fine with the CVS code from > 2.3.0b2. I didn't get to check b3 - we had a public holiday on Friday and > that meant that the one working day assigned to the b3

Re: [Zope-dev] 2.3.0 release badness

2001-01-29 Thread Martijn Faassen
Chris Withers wrote: [snip] > Sometimes, it'll just sit there redirecting back to the css page infinitely.. > yum :-S Yeah, I've seen that kind of weirdness show up too occasionally; some kind of infinite css getting loop in Netscape. A couple of times I've seen it blow up the server logs; I susp

Re: [Zope-dev] 2.3.0 release badness

2001-01-29 Thread richard
Pablo Bleyer Kocik wrote: > Nope, this is not only a problem of 2.3.0. I have had the same issue in all > of the 2.3.0x Zope versions, and the problem is not really Zope but Netscape > 4.X. > > For me, the trouble arises once in a while and specially when I start doing > page reloads quic

Re: [Zope-dev] 2.3.0 release badness

2001-01-29 Thread Adrian Hungate
Does the same occur if you serve using something else ('DTML Method', 'File', 'ZStyleSheet' etc) I have noticed problems with Netscapes handling of Text/CSS stylesheets. It appears that long or particularly complex stylesheets that can be (And here is the kicker) downloaded too quickly, do not se

RE: [Zope-dev] 2.3.0 release badness

2001-01-29 Thread Seb Bacon
Of Steve Alexander > Sent: 29 January 2001 17:07 > To: Shane Hathaway > Cc: [EMAIL PROTECTED] > Subject: Re: [Zope-dev] 2.3.0 release badness > > > Shane Hathaway wrote: > > > [EMAIL PROTECTED] wrote: > > > >> Of course, embedding the style in the page (a-l

Re: [Zope-dev] 2.3.0 release badness

2001-01-29 Thread Chris Withers
Shane Hathaway wrote: > > It seems to occur on Unix versions only AFAIK. When you visit a page > with linked CSS, visit another page, and come back, sometimes a portion > of the page is replaced with the text of the CSS. I don't have a URL. i've had a nice variant of this in Windoze Nutscrape.

Re: [Zope-dev] 2.3.0 release badness

2001-01-29 Thread Shane Hathaway
Steve Alexander wrote: > > Shane Hathaway wrote: > > > [EMAIL PROTECTED] wrote: > > > >> Of course, embedding the style in the page (a-la the Zope management > >> interface) gets around this problem, but this is not an option for us. > > > > > > This is a known bug in Netscape. > > I'm intrigue

Re: [Zope-dev] 2.3.0 release badness

2001-01-29 Thread Steve Alexander
Shane Hathaway wrote: > [EMAIL PROTECTED] wrote: > >> Of course, embedding the style in the page (a-la the Zope management >> interface) gets around this problem, but this is not an option for us. > > > This is a known bug in Netscape. I'm intrigued to know what causes it (in more detail tha

Re: [Zope-dev] 2.3.0 release badness

2001-01-29 Thread Shane Hathaway
[EMAIL PROTECTED] wrote: > Of course, embedding the style in the page (a-la the Zope management > interface) gets around this problem, but this is not an option for us. This is a known bug in Netscape. The management interface does user-agent sniffing; "Mozilla/4*" that doesn't contain the strin

Re: [Zope-dev] 2.3.0 release badness

2001-01-28 Thread Pablo Bleyer Kocik
> the HTML's header) and then a sort of synchronizing error happens. When you are > at the local machine the delay between the document requests is larger so the Oops. That should be "When you are *not* at the local machine...". Sorry ;^) -- Pablo Bleyer Kocik | pbleyer|"Rintrah

Re: [Zope-dev] 2.3.0 release badness

2001-01-28 Thread Pablo Bleyer Kocik
[EMAIL PROTECTED] wrote: > I've just updated to 2.3.0 release using CVS. My CSS serving has > subsequently broken. The CSS serving worked fine with the CVS code from > 2.3.0b2. I didn't get to check b3 - we had a public holiday on Friday and > that meant that the one working day assigned to the b

[Zope-dev] 2.3.0 release badness

2001-01-28 Thread richard
I've just updated to 2.3.0 release using CVS. My CSS serving has subsequently broken. The CSS serving worked fine with the CVS code from 2.3.0b2. I didn't get to check b3 - we had a public holiday on Friday and that meant that the one working day assigned to the b3 release was lost to me (and _mos