I can only assume this is some type of javascript lockup. Also, I hadn't noticed this problem prior to ICEfaces 1.7RC1

In order to reproduce, follow these steps:

1. Download and Install the Liferay 4.4.2 + Tomcat 6.0.16 bundle
2. Run the bundle, which will create a $HOME/liferay/deploy folder
3. Download the sample-icefaces-jsf-1.1-myfaces-jsp-portlet-4.4.1.1.war attached to this ticket and copy to $HOME/liferay/deploy
4. Download the sample-icefaces-jsf-1.1-sun-facelets-portlet-4.4.1.1.war attached to this ticket and copy to $HOME/liferay/deploy
5. Start IE7 (that's the key, since I can't reproduce this with FireFox or Safari)
6. Login as test@liferay.com with password test
7. Position the mouse over the "Welcome" dock in the upper right hand corner
8. Navigate to "My Places > My Community > Private Pages"
9. Add a page named "ICE MyFaces"
10. Add a page named "ICE Sun"
11. Click on the "ICE MyFaces" tab, and add the "Sample ICEfaces JSF 1.1 MyFaces JSP" portlet from the "Samples" category
12. Click on the "ICE Sun" tab, and add the "Sample ICEfaces JSF 1.1 Sun Facelets" portlet from the "Samples" category
13. Start tabbing through the fields of the portlet. Most of the fields are REQUIRED, and if you tab-out without entering anything you should see D2D show a FacesMessage next to each field.

At this point, the first portlet you're trying may or may not work fine. If the FacesMessages are not showing up, then click on the date picker and you'll find that IE7 locks up. It will eventually unlock itself after a few minutes.

If the portlet was working OK after tabbing, meaning, you saw FacesMessages, then click on the other "ICE Sun" tab and start tabbing through there. Eventually it will lock up.