[Seaside] Problems when using #script and #style Methods
philippe.marschall at gmail.com
Mon Feb 22 18:05:06 UTC 2010
2010/2/22 Karsten <karsten at heeg.de>:
> I've noticed that in one of our projects we still have #style or #script
> methods. I discovered that there seem to be some weird problem where Firefox
> gets the wrong content from these methods. We have 2 Components in one
> parent Component and both components have a style method. There's also
> another Component that has a #script method. Sometimes it happens that one
> of the components has the style of the other component, while in other cases
> a css-file is used, where a script should have been returned.
Do you dynamically change the contents of #style and #script or does
Firefox / Seaside do something funky?
> What's strange
> though is that in the WAApplication's cache, there's the right content for
> the right key, while in Firefox the wrong content is received.
If you manually issue a GET request (wget, curl, ...) do you get the
right content? What happens if you debug a manually issued GET
> It doesn't always happend and it's sure hard to reproduce, but it happens a
> lot here.
> Does anyone have an idea what's going wrong there?
Not directly but we discourage #style and #script on components. OTOH
it could be a problem with WARegistry/WACache that could hit us in
other cases as well. I don't suppose you have a minimal test case?
More information about the seaside