>I think this is an issue with UIData using a very >poor algorithm for when it thinks it can drop state, >something like "there weren't any errors." >The ADF UIXTable code has a better algorithm >hat doesn't suffer from this problem.
So is UIData's poor algorithm a spec issue or an implementation issue? Its great that UIXTable doesn't suffer from these problems but it would be nice if the standard UIData didn't suffer from these problems either. :) I'm just unsure who I need to be lobbying. Can anyone give me some direction? Mike
