Yes, I actually wound up doing this, but I think there is a better solution, since this solution is a hack. Basically, the problem lies with the Grid's pager, which does not work if inPlace = true and JavaScript is disabled. There links in the pager probably could be gracefully degraded if JS is disabled, but they are not currently. I know this is probably not as easy as it might appear, that's why I raised the issue and if it was easy it would probably be done by now :)
On Oct 9, 2011, at 3:19 PM, Muhammad Gelbana wrote: > The grid component is generated server-side, so on server-side, you have to > know if the client has JS enabled. I have no idea how to do this but I > "think" I read something similar here on the list lately, something about > checking the request object I suppose. > > Anyway if that's possible, bind the inPlace attribute to your page using a > prop prefix: > *t:inPlace="prop:yourDecision"* > * > * > And obviously using a *public boolean getYourDecision()* will solve the > situation...I think :D..didn't try this before but done something similar. > > On Tue, Sep 20, 2011 at 3:50 AM, Lenny Primak <lpri...@hope.nyc.ny.us>wrote: > >> When I have inplace set for a grid, and JavaScript is disabled, the pager >> buttons do nothing. >> How do I make it turn on only when JavaScript is available? >> Thanks! >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> > > > -- > *Regards,* > *Muhammad Gelbana > Java Developer* --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
