Based on ChatGPT suggestion
some places use kebab-case some places use camleCase.
For capture-app-iframe
- find all postMessage.data and make sure all are kebab-case
QA verified method: iframe back button ( Top left corner )
QA summarised the testing cases about it. https://miro.com/app/board/o9J_knEiIYo=/?moveToWidget=3458764546039920899&cot=14
Testing case A : fixed on android, iOS not yet. → Also happened on live version fixed in the future.
Testing case B: fixed
Testing case C:
- If v230209-iframe deploy and v230209-ionic haven’t been public -> the back button can’t work in data & terms.
- Before iframe-v230209 deploy, the back button can work normally in data & terms.
- v230131-iframe & ionic should not influence the back button.
Testing case D: known issue ✓ [issue] back button will back to wrong page (should in the explore tab not my capture tab)
At least fixed B & C, A & D could be fixed in the future sprint.
┆Issue is synchronized with this Asana task by Unito
┆Created By: Sam