Custom chrome tabs erases text area input when switching activities |
||||
Issue descriptionVersion: Chrome 53.0.2785.124 OS: Android 7.0 What steps will reproduce the problem? (1) Open http://westseattleblog.com/2016/10/bicycle-rider-taken-to-hospital-after-47thgenesee-incident/ in a link from the Twitter app in a custom chrome tab (2) Type a long comment into the text area at the bottom of the page (3) Switch to regular Chrome to copy-paste some text into the comment I'm editing What is the expected output? When I switch back to Twitter (open to the custom tab), the text I typed is still in the text box. What do you see instead? The page refreshes and the text disappears. I want to throw tablet across table. Please use labels and text to provide additional information.
,
Oct 21 2016
Chrome on Android has a general issue that we can only keep so many tabs in memory before Android begins killing them. Ideally, we could keep at least two in memory though (one being CCT, the other Chrome). When you switched to Chrome, were you already on the tab that contained the text you wanted to copy or did you end up having to switch through multiple tabs to get there? The more tabs you visit the more likely the other tabs will get killed in the background. +lizeb@ as they'll know more about the process priority While I have no idea if it will help, I added tab persistence to Custom Tabs in M54, and I "believe" that it attempts to save text entered into the tab when doing a restore. So maybe this will get better in the next release.
,
Oct 21 2016
In Chrome, I think I opened a new tab and did a Web search to find the text to copy-paste. I'm accustomed to text area persistence across navigation and am surprised it's not fully supported on session restore.
,
Oct 23 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 8 2018
We've added the same restore logic as Chrome to CCT, so I don't think there is anything more we can do here if it is still a problem. You could try with "Don't keep activities" in Android to verify, but if it still happens, we should file a general bug about restore and not about CCT. |
||||
►
Sign in to add a comment |
||||
Comment 1 by jay...@chromium.org
, Oct 21 2016Status: Available (was: Untriaged)