> How about getting rid of the base-uri slot altogether? That way, > navigation would render relative URLs, code would be simpler, and would > work better. > > The only other use for base-uri is code that redirects to the first pane > if no default pane was provided. I do not think we can redirect to a > relative URL, but I don't see a big need for this functionality. And > perhaps someone can think of a solution not involving base-uri here?
The current base URI might be useful for more elaborate purposes (building links, specifically). But let us get rid of BASE-URI and think of another solution later as needed. But what worries me is how the flow-introduced nav will decide on its children if it's not instructed specifically to do so. The current code might account for that, of course; I haven't checked. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
