This screenshot shows how the paginator in the component showcase looks like after switching to "Columns" and back.

Cannot reproduce this with any of our test browsers using 1.8.0-RC2.

Please provide additional information:

• Operating system/platform + browser and version being used?
• Exact steps to reproduce the problem
• Any special conditions required to reproduce the problem (browser window size, theme, etc.).

I have it too, but I could not get the Component Showcase latest build on icefaces.org to do this.
But it does happen with my own projects and this definitely started with 1.8.0. RC2.
It happens when I change the number of rows in the table using the combo box.

Product Version: NetBeans IDE 6.5 (Build 200811100001)
Java: 1.6.0_11; Java HotSpot(TM) Client VM 11.0-b16
System: Windows XP version 5.1 running on x86; Cp1252; nl_NL (nb)
Userdir: C:\Documents and Settings\Marcel\.netbeans\6.5

IE7 with all fixes

GlassFish V2UR2

Okay, this can be seen using the JSP variant of the component-showcase (/samples/component-showcase/jsp). Note that for some reason the facelet and facelet-enh versions do not have this issue.

To reproduce, simply view the dataPaginator demo in any browser, click "2" to go to page 2, and the problem appears.

I created a little test project to reproduce the issue, NetBeans project is attached

Server: JBoss 4.2.3-jdk6 on jdk-1.6.0_12 on Linux / x86-64 (but exhibits this on Windows XP / x86-32 as well)
Browsers: IE 7 Version 7.0.5730.13, Firefox 3.0.7, both on Windows XP

To reproduce use the jsp-showcase

• choose any theme
• click on Table / Data Paginator (looks fine now)
• click on Columns
• go back to Data Paginator

You then get the presentation shown in the first screenshot.

Disabled DOM optimization that revealed this problem. Note that the function of the optimization is to disable error checking on DOM operations, so the component should still be investigated for possible DOM manipulation errors.

Could a patched jar be made available, like Frank did for ICE-4262?
This makes it easier to test the change before 1.8.0 final release

Invoke the following static method from your application code to disable the optimization (the checked in change simply turns the optimization off by default):

DOMResponseWriter.setDOMErrorChecking(true);

If I understand this correctly, dataPaginator needs further investigation to make it behave nicely.
Is this planned for 1.8.0 final?

The change that was incompatible with the paginator (actually the commandLink used by the paginator) has been reverted, so there should be no revisions to the paginator required for 1.8.0 final. In any case, please test from subversion to verify in your application, or contact product.support@icesoft.com for an interim binary for testing.

Hi,

Last svn rev 18675 perfectly works.

regards,