Improve tab switcher screenshot quality |
|||||||||
Issue descriptionCurrently, the tab switcher oftentimes uses low quality screenshots. Repro: - open a couple of tabs - open the tab switcher - look for one of the "older" tabs Expected: - great screenshot quality Actual: - compression artefacts This has previously been a conscious implementation decision, see Issue 357740. We should re-evaluate our options to make sure we can improve the UX (this is pretty jarring)
,
Jun 22 2016
,
Jul 6 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 19 2016
Hi, this is visible on all devices and all Chrome on Android channels. For comparison, please find attached screenshots from: A: the Android recents view B: Chrome on Android tab switcher with "the Independent" tab *not* being the last tab open C: the same with the same tab being the last tab open You can see that the quality of the Independent tab in B is considerably worse than in the other cases.
,
Jul 19 2016
My guess is in case B the tab image is not live from the renderer, but it's the screenshot saved on disk, which is lower quality.
,
Jul 19 2016
Exactly, and I'd like to figure out how we can improve those. :)
,
Jul 25 2016
OK, the screenshots looks like the expected ETC1 artifacting, not a bug. Like Daniel, I'd suggest first trying out ETC2 on GLES3-supporting devices and see if the quality and performance is satisfactory.
,
Aug 12 2016
Let's try this out in the M55 time frame.
,
Oct 5 2016
,
Nov 21 2016
,
Nov 21 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 13 2018
+cblume, should this be marked as a duplicate of issue 748648 or issue 794314 ?
,
Feb 13 2018
All three of these issues seem like duplicates to me. That said, I somehow completely missed issue 748648 being assigned to me back in Oct. This is the first I heard of this bug. I can perhaps help with any png / etc1 / etc2 questions. But I know very very little about our tab switcher code. I touched it once and may have even introduced a bug when doing so. :) Probably best to reassign all these to someone on the Clank team.
,
Feb 14 2018
I believe the three bugs are really about quality of the screenshot used in the tab switcher more-so than the tab switcher animation code. Given the age of this bug, and inactivity thus far, if you're not the correct owner I think it's fine to move to P3/Available. Issue 748648 has the most context, so I'd de-dupe into that one as needed.
,
Feb 14 2018
In issue 748648 it seemed more like we were creating images of the wrong size. The problem went away once the images were created at the correct resolution. So I don't think it is about the quality of the image.
,
Feb 14 2018
Oh whoops. I read what you said as "dupe into that one". But while duping issue 794314 , I saw your comment about NOT duping because issue 748648 is marked Restrict-View-Google. Presumably, we could mark that as a dupe of one of these and just note that more details are available there?
,
Feb 14 2018
I think it's okay to dupe against the RVG bug since everyone on this thread should have access. We can copy details back here if needed. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by aelias@chromium.org
, Jun 22 2016