Thanks.
Eelco
On 11/13/06, Erik van Oosten <[EMAIL PROTECTED]> wrote:
> Ok.
> http://issues.apache.org/jira/browse/WICKET-58
>
> Erik.
>
>
> Eelco Hillenius wrote:
> >> You need to set the target attribute when you need to support a
> >> non-JavaScript browser. Otherwise, the target attribut
Ok.
http://issues.apache.org/jira/browse/WICKET-58
Erik.
Eelco Hillenius wrote:
>> You need to set the target attribute when you need to support a
>> non-JavaScript browser. Otherwise, the target attribute won't explain
>> the problem Neli is having unless a weird browser is used.
>>
>> I w
> You need to set the target attribute when you need to support a
> non-JavaScript browser. Otherwise, the target attribute won't explain
> the problem Neli is having unless a weird browser is used.
>
> I was just surprised the target attribute was not set automatically as I
> thought Wicket's phil
Hi Neli, Eelco,
You need to set the target attribute when you need to support a
non-JavaScript browser. Otherwise, the target attribute won't explain
the problem Neli is having unless a weird browser is used.
I was just surprised the target attribute was not set automatically as I
thought Wick
I the current version of Wicket the target is set on bookmarkable
links when you explicitly set the target on the link itself. You don't
need this for popups though, as this is the window name you're passing
in.
window.open(getReportUrl(), 'myReport' <---
If you look at the url:
'/mypath//MyRep
onComponentTag of Link does not write any target attribute.
It looks like the bookmarkable page is not entered to the proper page
map so renderHead in WebPage sets window name to "wicket:default".
Erik van Oosten wrote:
> Should this not also include a target attribute, e.g. target="myReport"?
>