State is forgotten when item is re-rendered

[jamesfzhang]

I have a list of radio buttons, each can be toggled by tapping. When I toggle a radio button, scroll away and scroll back to it, the radio button resets to the original state. Is this intentional?

EDIT: The radio button's getInitialState sets its toggled state to be on. I'm guessing that when an item leaves the current viewport, it gets destroyed completely and then re-drawn when it comes back into view. Therefore, the item is re-rendered completely getInitialState gets called again.

[sghiassy]

Probably. The list view works by destroying views after they've scrolled off screen, so state would probably have to be persisted for items like radio buttons.

[rameshvishnoi90904]

its works fine i.e state or props does not revert back in Android, but in IOS state or props values does get revert back.

[sghiassy]

I could perhaps add a props flag that you can set per cell, for the View not to be destroyed when it scrolls out of view. Would that help? You'd loose the performance benefit, but if you set it selectively for just some cells, it might still be helpful.

Let me know how helpful that'd be

[sghiassy]

Maybe keepAlive={true} or something. Default would be keepAlive={false}

[mschipperheyn]

In many case state should be replaced by props anyways. I wonder if supporting this case, is worth it and if the same effect cannot be achieve by developers rewriting their code to depend more on props (good) in stead of state (bad).

[sghiassy]

@mschipperheyn - fair point