|
|
|
|
|
by acdha
1187 days ago
|
|
That part is amazing: it calls into question the entire Android code review process that nobody thought breaking compatibility wasn’t a problem, much less doing so in a way which looks like one of the most familiar interfaces in the world. It seems unlikely that this isn’t just the first, most visible bug. |
|
There were no unit tests written for the original implementation, but they did update the tests for the refactored function [1], and the tests clearly show different behaviour from the original implementation [2].
My best guess would be that the code wasn't reviewed.
[1] https://cs.android.com/android/_/android/platform/frameworks...
[2] https://cs.android.com/android/_/android/platform/frameworks...