Unsaved form in the activity AccountsActivity and WebViewActivity

[davirec]

Hi, this issue has relation with #202

When executing this sequence of actions, there is a loss of data in the activity AccountsActivity:

IntentEvent(intent='am start com.etesync.syncadapter/com.etesync.syncadapter.ui.AccountsActivity') KeyEvent(name=BACK) IntentEvent(intent='am start com.etesync.syncadapter/com.etesync.syncadapter.ui.AccountsActivity') ScrollEvent(direction=FULL_RIGHT) TouchEvent [[540,778],[652,862]] FillUIEvent

Cap01: capture screen properties before rotation DoubleRotationEvent Cap02: capture screen properties after rotation

Cap01 != Cap02 (incompatible sizes)

When executing this sequence of actions, there is a loss of data in the activity WebViewActivity: TouchEvent [[35,558],[692,614]] ScrollEvent(direction=FULL_LEFT) KeyEvent(name=BACK) IntentEvent(intent='am start com.etesync.syncadapter/com.etesync.syncadapter.ui.AccountsActivity') DoubleRotationEvent KeyEvent(name=BACK) IntentEvent(intent='am start com.etesync.syncadapter/com.etesync.syncadapter.ui.AccountsActivity') TouchEvent [[594,1432],[692,1530]] TouchEvent [[0,54],[98,152]] TouchEvent [[0,54],[98,152]] TouchEvent [[0,686],[490,770]] TouchEvent [[113,1317],[411,1357]] ScrollEvent(direction=FULL_RIGHT) ScrollEvent(direction=UP) [[0,152],[722,1560]] TouchEvent [[176,496],[497,538]] FillUIEvent

Cap01: capture screen properties before rotation DoubleRotationEvent Cap02: capture screen properties after rotation

Cap01 != Cap02 (Loses screen state: scroll)

Note:

• Double screen rotation (DoubleRotationEvent): It is executed twice to reach a state that should be exactly the same as the screen before if no data loss occurred.
• A data loss problem occurs when data is accidentally deleted or state variables are accidentally assigned with default or initial values.

[tasn]

Please don't write dataloss in the title and give me a heart attack. It's not a data loss. :)

[davirec]

Hi tasn! Sorry about that :) If I need to open similar issues in the future, what is a term that you think better characterizes this issue?

[tasn]

I think "unsaved form" is probably a good description.