Jan Rychter wrote:
> -- after some actions are executed, the DOM ends up with duplicate > widgets contained within one another, as in: > > <div id="id7" class="blah widget"> > <div id="id7" class="blah widget"> > ... > > I remember there was a javascript change that instead of setting > innerHTML replaced the child of a widget parent -- could that be > responsible? That sounds likely. > -- if I follow a link to a page with a fragment identifier > (/someplace#somewhere), actions do not work on that page. They simply > do nothing when clicked. I've noticed that one too but haven't made any endeavours to track it down yet. You might want to check TOKENIZE-URI, GET-REQUEST-ACTION and HUNCHENTOOT:REQUEST-URI* for clues. It may also help to look into the request header that gets sent by the browser. Leslie --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
