This is a list of questions and issues regarding Deliverance that need looking into.

• When a rule matches both a tag and a tag nested inside the first tag, what should be done?  produce an error or only include outer tag ? eg in copy; currently both are produced
• Depending on their context, some relative links in the theme will not be made absolute? eg relative links in mouseover javascript; this is probably outside the scope of deliverance?
• What are the cross site scripting implications of xincludes in the theme?
• Should we enforce the style sheet precedence between theme and content? probably content styles / meta should take precedence
• for the append-or-replace rule: should the elements replaced in the theme be more related to the full xpath used to match content elements?  Currently we just replace based on tag type, not on attribute values.
• nested moves are not supported, ie moving an element "then" moving its parent
  

• Dealing with bad html

What to do about:
- html comments with "--" in the body of the comment will break the xslt renderer
- if the <meta http-equiv="content-type"> that specifies the character encoding comes after non-ASCII characters on the page, the output will not preserve the encoded text

• Avoid theming AJAX responses
  

we currently use a heuristic to ignore content that not html or is only an html snippet, but this may need to be more robust.  David had the idea of rewriting the javascript XMLHttpRequest so that it always calls with some marker that could be detected.

• Avoid theming popups
  

See Current Tasks
See Scaling