Assigned
Status Update
No update yet.
Comments
ha...@google.com
no...@google.com
Project: platform/frameworks/support
Branch: androidx-master-dev
commit 41c9e54ce4ab51f95d19a55fa92a56b6bd018c62
Author: Ian Lake <ilake@google.com>
Date: Mon Mar 23 16:07:32 2020
Allow obfuscation of kept Fragments
Fragments that are kept solely by class
can safely be obfuscated.
By switching to keepclasseswithmembers,
only classes with a default constructor
will qualify to be kept. This also allows
shrinking of classes that are constructed
through a custom FragmentFactory.
Test: tested in sample app at
BUG: 151605338
Change-Id: I68ea8779bce80f33f27658cf87a94ccede5376b0
M fragment/fragment/proguard-rules.pro
https://android-review.googlesource.com/1266484
Branch: androidx-master-dev
commit 41c9e54ce4ab51f95d19a55fa92a56b6bd018c62
Author: Ian Lake <ilake@google.com>
Date: Mon Mar 23 16:07:32 2020
Allow obfuscation of kept Fragments
Fragments that are kept solely by class
can safely be obfuscated.
By switching to keepclasseswithmembers,
only classes with a default constructor
will qualify to be kept. This also allows
shrinking of classes that are constructed
through a custom FragmentFactory.
Test: tested in sample app at
BUG: 151605338
Change-Id: I68ea8779bce80f33f27658cf87a94ccede5376b0
M fragment/fragment/proguard-rules.pro
no...@google.com
While -keepclassmembers caused a regression in the allowsObfuscation to allow even kept fragments to be obfuscated.
This will be available in the upcoming Fragment 1.2.4 and 1.3.0-alpha03.
Description
It appears that Android renders U+2029 PARAGRAPH SEPARATOR in various apps as a square (i.e.
You can see this in the this Mastodon bio:https://ruby.social/@helvetic_ruby or as a screenshot in the attached screenshot.
It probably goes without saying but it looks fine in browsers or on iOS.