Googling a bit, I assume that Wt does not really provides the means to support named-anchor navigation.
Probably since Wt is more GUI-centric and not document-centric. I guess the Wt answer would be to use a WTabWidget, a WStackedWidget or something like that instead of named-anchors. http://stackoverflow.com/questions/5426007/ajax-and-scroll-to/5426097#5426097 discusses the ajax #-style url schemes (which in a way conflict with named-anchors) and provides some further links. Since Wt does some url mangling and uses different url schemes depending on if java-script is available or not, one would need some Wt widget implements workarounds for named-anchor navigation (if java-script is available, implement the scrolling to a named-anchor via java-script etc.). Best regards Georg PS: On 2011-06-01, Georg Sauthoff <[email protected]> wrote: [..] > - Looking at the html code inside chromium ('inspect element') yields > 503 matches of 'my_anchor' - why? Inside firefox ('View selection > source') the '<a name="my_anchor"/> is also duplicated several times > when looking at the source Right now looks like a bug - I probably report it in the Wt bug-tracker. ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
