[Seaside] Problem loading css in updateRoot:

Philippe Marschall philippe.marschall at gmail.com
Wed May 28 09:07:33 UTC 2014

On Wed, May 28, 2014 at 9:01 AM, jtuchel at objektfabrik.de
<jtuchel at objektfabrik.de> wrote:
> Hi,
> I tried adding a css file from a WAFileLibrary sublass to only one
> component, because it is really just needed on pages that use the
> WAComponent that refernences it. The reason is that if you use
> #selectorsToInclude on the file library, the css will be imported into every
> single page. It is a larger css file, and since our production server uses
> https, I'd like to avoid importing too much.
> So I implemented this:
> updateRoot: htmlRoot
>    super updateRoot: htmlRoot.
>    htmlRoot stylesheet beCss url: KontolinoFileLibrary / #buaDetailsCss.

That's implemented in a specific component class of yours?

> I either don't understand the purpose of updateRoot: completely or there is
> some problem with this approach:
> In IE 11 and Safari 7.0.4 as well as Firefox 29, the css link is not always
> in the head-section of the resulting page.

The browser should not matter since it's either in the HTML or not.

> But is there if I hit the
> Browser's reload button on the page. This is quite consistently so, but in
> maybe 3 out of 25 tries the css is also in the page when I navigate to it by
> call: or show:
> So far I only tried that locally with direct http access to the image
> (development machine), no front-end http server.
> Am I trying to do something at the wrong place - should I use another method
> for this?
> Is this a bug in Seaside? I have only tried in VA Smalltalk so far...

Are you using AJAX?


More information about the seaside mailing list