absolutely, (but you will need to escape the # since it might
be taken for a directive)
I just wanted input from everyone regarding this. From a web designer's
view point it seems that
$link.setPage("admin,index.wm#markMe")
is more friendly than
$link.setPage("admin,index.wm")\#markMe
but it doesn't bother me that much. That's why I am holding
off on any commit's on the fix.
mike
On Tue, Nov 28, 2000 at 10:25:35AM -0800, John McNally wrote:
> Mike Haberman wrote:
> >
> > It seems that in order for named anchors to work properly, the '#'
> > must not be encoded (via URLEncoder). I would think that browsers
> > should be able to handled the encoded '#' but they don't.
> >
> > I have the fix and am ready to commit it to cvs, but was wondering
> > if anyone else has any comments on this.
> >
> > This will affect any calls to $link.setPage() that contain a hash
> > mark.
> > e.g $link.setPage("admin,index.wm#markMe")
>
>
> Can't this be avoided by defining the link like this?
>
> e.g $link.setPage("admin,index.wm")#markMe
>
>
> >
> > Also, there is a lot of unnecessary object (StringBuffer) creation.
> > I will commit the fix for that as well.
> >
> > let me know,
> >
> > mike
> >
> > ------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
> > Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> > Problems?: [EMAIL PROTECTED]
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
