[ http://issues.apache.org/jira/browse/BEEHIVE-331?page=history ]
     
Krista Baker closed BEEHIVE-331:
--------------------------------


Verified - based on above determination that the getNetuiTagName and 
netui_names tagId functionality is this way on purpose.  

> html scope not recognized by legacy tags when in a scriptContainer
> ------------------------------------------------------------------
>
>          Key: BEEHIVE-331
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-331
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1
>     Reporter: Krista Baker
>     Assignee: Krista Baker
>  Attachments: J331.jsp
>
> When a netui:html tag has a scopeId and subsequent netui html tags are 
> contained in a scriptContainer that has no scopeId set, the netui_names 
> tagName generation does not include the html scope.  
> Removing the scriptContainer tag or adding an idScope attribute to the tag 
> fixes the above problem of not writing out the expected netui_name including 
> the scope.
> Also, if a nested scriptContainer tag is added with a scopeId attribute the 
> netui_names javaScript produces expected results.
> Actual Results:
> (See attached jsp):
> This issue is not just on the anchor tag, this has also been viewed on tags 
> that generate names (netui:textBox).  The lookupNameByTagID function works as 
> expected, but the getNetuiTagName function returns undefined.
> The first anchor name is undefined, a look at the source code shows that it 
> does not pick up the scopeId from the html tag.  (Generated JavaScript:  
> netui_names.tb1="one.tb1" and netui_names.one__tba1="one.tba1") Note that the 
> one in the scriptContainer does not include the scope set in the html tag.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Reply via email to