Comment #5 on issue 1071 by felix8a: Cajoler resolves embedded URIs too early
http://code.google.com/p/google-caja/issues/detail?id=1071 I vote for resurrecting the 3-arg PluginEnvironment. I originally filed the bug in reaction to trying to support <a href="#foo"> which is used by yui's tabview. I think semantic fragments are also used by other js libs, but I don't have any examples handy. in the case of tabview, the #foo is semantic markup. if js is off, then you see the tabs as a series of blocks, and the tabs header is a <ul> that's a table of contents, and clicking on a name in the tabs header will navigate to that block. when js is enabled, the js finds the tabview markup, and modifies it to look like a rich tabbed widget, and this relies on the js being able to parse href="#foo" if someone resolves the href into href="http://....#foo"; then the tabview doesn't work any more. it's not clear to me that there's any way to fix it other than "don't resolve the fragment". there isn't any way for the cajoler to know what the right http://... is, since the cajoler doesn't know how the page is going to be embedded in a container. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
