This issue should still be present. When this issue was investigated there was a separate pagination issue presenting in the POC.
I will test later today to confirm.

An issue very much like this one appears to be effecting the decoding of components in pages greater than 1.

This is because visitTree is receiving the incorrect value from getFirst(). visitTree relies on getFirst() to tell it where to begin per-row visiting, and getRows() to determine row far to iterate.

At the end of a request that causes pagination, getFirst() returns the correct value, at the beginning of following requests, getFirst() returns 0, and visitTree incorrectly performs per-row visits for the first page of components.

The easiest way to reproduce this error is by adding pagination to an example of row editing, like the Row State example on the comp-suite.

Debugging the DOMPartialViewContext.processPartial method:

if (phaseId == PhaseId.RENDER_RESPONSE) {
try {
PartialResponseWriter partialWriter = getPartialResponseWriter();

...
if ((null == oldDOM) && isRenderAll())

partialWriter.endDocument();

When use the ACE paginator, neither the "if" or "else if" section is meeting the condition so the renderState() and renderExtensions() are never called. It looks like it's a result of the custom update processing that the ACE components do to calculate their own updates. The renderState() section is what calls getViewState and triggers the view state to be saved. By factoring the renderState() and renderExtension() calls so that they are always invoked, the problem goes away.

if (phaseId == PhaseId.RENDER_RESPONSE) {
try {
PartialResponseWriter partialWriter = getPartialResponseWriter();

...
if ((null == oldDOM) && isRenderAll())

renderState();
renderExtensions();
partialWriter.endDocument();

Checked in change (r25908) to DOMPartialViewContext.