On Thursday 08 September 2005 05:49, Martijn Faassen wrote:
> If not, then my complaint is that 'for' only accepts interfaces, not
> classes, while the 'for' for the page directive also accepts classes.
>
> So, as far as I understand, I am not trying to use defaultView for
> anything but specifying
Martijn Faassen wrote:
Martijn Faassen wrote:
Jim Fulton wrote:
Martijn Faassen wrote:
While the browser:page directive can take a content class for its
'for' attribute (instead of an interface), the browser:defaultView
directive doesn't accept this. I tried changing the interface of the
Martijn Faassen wrote:
Jim Fulton wrote:
Martijn Faassen wrote:
While the browser:page directive can take a content class for its
'for' attribute (instead of an interface), the browser:defaultView
directive doesn't accept this. I tried changing the interface of the
defaultView directive so
Jim Fulton wrote:
Martijn Faassen wrote:
While the browser:page directive can take a content class for its
'for' attribute (instead of an interface), the browser:defaultView
directive doesn't accept this. I tried changing the interface of the
defaultView directive so it also accepts classes,
Martijn Faassen wrote:
Hi there,
While the browser:page directive can take a content class for its 'for'
attribute (instead of an interface), the browser:defaultView directive
doesn't accept this. I tried changing the interface of the defaultView
directive so it also accepts classes, but that
