[ http://issues.apache.org/jira/browse/BEEHIVE-500?page=all ]
Carlin Rogers resolved BEEHIVE-500:
-----------------------------------
Assign To: Krista Baker (was: Carlin Rogers)
Resolution: Fixed
Nice catch on the XmlHttpRequest issue.
I'd like to have this bug resolved as originaly
described and fixed, then track the XmlHttpRequest
problem as a separate issue. I have opened up
a Jira bug for the boundary case identified.
see JIRA beehive-609...
http://issues.apache.org/jira/browse/BEEHIVE-609
> netui tags generated URLs are not HTML compliant
> ------------------------------------------------
>
> Key: BEEHIVE-500
> URL: http://issues.apache.org/jira/browse/BEEHIVE-500
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1Beta
> Reporter: Krista Baker
> Assignee: Krista Baker
> Fix For: V1
> Attachments: Controller.jpf, Controller.jpf, basicJSPTree.jsp,
> expandModes.jsp
>
> When creating a tree (except runAtClient trees), the expansion and selection
> actions are generated as anchor hrefs which include the parameter of
> netui_treeid=tree. These generated URLs do not encode the & symbol into
> & when the document type is set to html4-loose, causing the following
> error when the html is run through an html validator: general entity
> "netui_treeid" not defined and no default entity.
> The generated XHTML when the document type is set to xhtml1-transitional is
> correctly encoded as &
> Example incorrect href:
> <a href="/basicPFTree/select.do?netui_treenode=0&netui_treeid=tree1">
> Example valid html href:
> <a href="/basicPFTree/select.do?netui_treenode=0&netui_treeid=tree1">
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
