For now, I would raise this as a bug and then we can address it at a later
date. This is an edge case that at the end of the day, just generates
invalid XHTML, rather than a gives broken application. Let's get the core
changes up and running and released, and then fix cases like this after.
Derek.
On 8/5/07, John Davidson <[EMAIL PROTECTED]> wrote:
>
> A normal topic created from the proposed default.aspx will now
> validate in XHTML 1.0 Transitional.
>
> There is one known bug (so far) where an uncreated topic reference in
> a property makes a nested anchor - one for the property anchor link
> and the second for the link to create the new topic. I know where this
> occurs, but did not see an easy solution.
>
> John Davidson
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Flexwiki-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/flexwiki-users
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Flexwiki-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
