Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Won't Fix
-
Affects Version/s: 2.0.0
-
Fix Version/s: None
-
Component/s: Framework
-
Labels:None
-
Environment:All
-
ICEsoft Forum Reference:
-
Workaround Exists:Yes
-
Workaround Description:If possible use a redirect navigation. Alternatively, wrap the entire page content inside the body tag with <h:panelGroup id="bodyGroup">
Description
After doing a forward navigation the body tag that is rendered gets its values set as "undefined". This causes a default browser tooltip to be displayed on the page. The body tag is rendered as the following:
Before:
<body>
After:
<body class="undefined" lang="undefined" style="" title="undefined" dir="">
This does not happen in a basic JSF (2.1.1 and 2.1.6 tested) test case.
Before:
<body>
After:
<body class="undefined" lang="undefined" style="" title="undefined" dir="">
This does not happen in a basic JSF (2.1.1 and 2.1.6 tested) test case.
-
Hide
-
-
META-INF/MANIFEST.MF
-
META-INF/context.xml
-
WEB-INF/lib/commons-beanutils.jar
-
WEB-INF/lib/commons-collections.jar
-
WEB-INF/lib/commons-digester.jar
-
WEB-INF/lib/commons-logging.jar
-
WEB-INF/lib/icefaces-ee-ace.jar
-
WEB-INF/lib/icefaces-ee-compat.jar
-
WEB-INF/lib/icefaces-ee-ext.jar
-
WEB-INF/lib/icefaces-ee.jar
-
WEB-INF/lib/javax.faces.jar
-
WEB-INF/lib/poi-3.7.jar
-
WEB-INF/web.xml
-
pageOne.xhtml
-
welcomeICEfaces.xhtml
-
-
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Salesforce Case | [5007000000LGFUA] | |
| Description |
After doing a forward navigation the body tag that is rendered gets its values set as "undefined". This causes a default browser tooltip to be displayed on the page. The body tag is rendered as the following: Before: <body> After: <body class="undefined" lang="undefined" style="" title="undefined" dir=""> |
After doing a forward navigation the body tag that is rendered gets its values set as "undefined". This causes a default browser tooltip to be displayed on the page. The body tag is rendered as the following: Before: <body> After: <body class="undefined" lang="undefined" style="" title="undefined" dir=""> This does not happen in a basic JSF (2.1.1 and 2.1.6 tested) test case. |
| Attachment | undefined-tooltip-firebug.jpg [ 14289 ] | |
| Attachment | Case11108Example.zip [ 14290 ] | |
| Attachment | Case11108Example.war [ 14291 ] |
| Fix Version/s | 3.1 [ 10312 ] | |
| Fix Version/s | EE-3.0.0.GA_P01 [ 10327 ] | |
| Assignee Priority | P1 | |
| Assignee | Ted Goddard [ ted.goddard ] | |
| Priority | Major [ 3 ] | Critical [ 2 ] |
This is due to the jsf.js function
var cloneAttributes = function cloneAttributes(target, source) {
which should be modified to use getAttribute() rather than element[attribute] and the values should be checked for null before copying into the destination. This results in undefined attributes being "copied" with value "undefined".
Show
Ted Goddard
added a comment - This is due to the jsf.js function
var cloneAttributes = function cloneAttributes(target, source) {
which should be modified to use getAttribute() rather than element [attribute] and the values should be checked for null before copying into the destination. This results in undefined attributes being "copied" with value "undefined".
| Workaround Description | If possible use a redirect navigation. | If possible use a redirect navigation. Alternatively, wrap the entire page content inside the body tag with <h:panelGroup id="bodyGroup"> |
| Summary | Undefined tooltip is shown after doing a forward navigation | IE browsers display "undefined" tooltip after doing a forward navigation |
| Fix Version/s | 3.1 [ 10312 ] | |
| Fix Version/s | EE-3.0.0.GA_P01 [ 10327 ] | |
| Assignee Priority | P1 | |
| Affects Version/s | 2.0.0 [ 10230 ] | |
| Affects Version/s | EE-3.0.0.GA [ 10262 ] | |
| Priority | Critical [ 2 ] | Minor [ 4 ] |
Mojarra bug filed:
Show
Ted Goddard
added a comment - Mojarra bug filed:
http://java.net/jira/browse/JAVASERVERFACES-2381
This is a mojarra bug (case is filed) and the workaround of wrapping the page content in a panelGroup should be reasonable in most cases.
Show
Ted Goddard
added a comment - This is a mojarra bug (case is filed) and the workaround of wrapping the page content in a panelGroup should be reasonable in most cases.
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Won't Fix [ 2 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
We have the basic navigation test (samples/core/test/nav) that is showing the same behaviour. The actual Ajax update doesn't seem to come back with those <body> attributes set to undefined so perhaps something in the bridge is doing some extra processing?It shows the same behaviour in that the body element ends up going from:
<body>
to
<body class="undefined" title="undefined" lang="undefined" dir="">
However, the navigation works for me and I don't see any popups or errors in the console (tried latest FF and Chrome). The test attached to this case in the JIRA works for me the same way - I see the body change but nothing else bad happens and the navigation works.