fd06bc8d6e83fc5b92192dedbc46eb70fb86198f
In the old navigation model, we set focus to a node, and checked to see if that node was still valid (could have changed since we built the navigation cache). Then we sent a message back to the UI thread to tell it to draw the ring differently. In the new model, we are essentially moving a mouse, so we do not concern ourselves with whether the node is valid. Removed all the code for passing the message to the UI thread and calling into native. Needs a change to external/webkit to work properly.
am
b42e1ff6: am b33940ab: AI 149494: Minor improvements to wording in design tips for missing activity and notifications See latest document at: http://doog:9000/guide/practices/ui_guidelines/activity_task_design.html
am
9189cabb: * Moved supports-density tag under manifest * Refactored Compatibility code * Added CompatibilityInfo class * Removed getApplicationScale from Context * Added Resources#getCompatibilityInfo so that RootView can get the compatibility info w/o going through Context * Expandable support * Added expandable tag under manifest * Old application w/o expandable is given the default screen size ([320, 480] x density). * The non-expandable window is centered.
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%