This seems to be related to using navigation. When the same app. is tested using redirect navigation, the error doesn't occur.

First error found with the test case occurs at line bridge.js:312 just as in the attached screenshot. The message was different since I could reproduce it only with FF. The problem seems to occur when iterating over a collection of script strings with the 'eval' function passed in as the iterator. The iterator would receive the code (as string) and the index of the string, at this point the JS interpreter would complain about the second parameter passed into the 'eval' function.

The fix applied makes sure that only the code is passed into the 'eval' function without additional parameters.

The second occurs while the DOM update is applied to the entire document. The update/document does not contain a title which causes the bridge code to fail while trying to extract the title from the update.

The fix applied checks first if the title exists before trying to extract the title content.

I'm finding jsp:forward is still failing for me but only if you close IE, clear the cache, and open it fresh again and then it only fails the first time with the original JS error that was reported.

Just to add my observations and notes. I saw the same reported error in the IE8 developer tools as reported originally. The error occurs in the Sizzle CSS library included with Prototype when it calls
Event.observe(window, 'load', fireContentLoadedEvent);

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Timestamp: Mon, 22 Aug 2011 18:18:28 UTC

Message: Object doesn't support this property or method
Line: 312
Char: 36
Code: 0
URI: http://192.168.55.107:8080/forum-ie8-arae/faces/javax.faces.resource/bridge.js;jsessionid=22842289F38D96A6B84B35BBAFE65154?rand=629435653

The problem occurs when:

• using IE8 (works fine with IE9 and non-IE browsers)
• navigation occurs that causes a ViewRoot update (so eval all the associated scripts again)
• it only happens immediately after IE8 has been started (it fails the first time but seems to work fine after that - presume a cached version of some resource is now working)
• depends on how you access the first page the first time:
• response.sendRedirect("faces/pages/Start.xhtml") works
• <jsp:forward page="faces/pages/Start.xhtml" /> does not work
• http://192.168.55.107:8080/forum-ie8/faces/pages/Start.xhtml does not work
  (at one point, it appeared that the FacesServlet mapping being set to /faces/* rather than *.jsf had some effect but the method of loading the first page is actually the real key)

When navigation is triggered an update is received for the entire document. The bridge will fetch the referenced scripts and evaluate them along with the inlined scripts.
When Prototype code is evaluated the context of evaluation is the one where the 'eval' function is invoked, context that has an Event variable already defined that differs from the global Event variable .

To fix the issue globalEval function was introduced which will evaluate inline and referenced scripts in the global context to avoid capturing private function or variable definitions.

This fix has been verified using trunk code rev. #25404, on tomcat 7, and browsers: IE8, Firefox 6.1, Google Chrome 13.
Closing the issue.

hi, my name is mark and have this problem, but i solutions. the solution is....
quit the <ice: inputs> and replace for <h:inputs> this way functions perfect... bridge is the problem, but this form is solution
good luck..
good bye.-