1. The query string was not converted to lower case during search
for infos with text.
bug:4818098
Change-Id: Ie4ba8ac2632072bdd71070ec8fd24ca255560ac0
1. While mapping Android hover to WebKit mouse events I was not
taking into account the horizontal and vertical scroll.
bug:4807087
Change-Id: Ie24a8a30ce6a20d27b627ae7c7fbff1b74d140c8
1. Updated the code to return empty list instead.
2. Updated the doc to explain that the search is done in the
sub-tree rooted at the info whose method is called.
Change-Id: I560d2563ed4772305bf2d7919560ef19baa30a1d
This adds a Java-language implementation of EventRecurrence.parse(),
to make it easier to relocate it for the benefit of unbundled
Calendar.
Differences from the native version:
- enforces that FREQ appears first
- allows (but ignores) X-* parts
- improved validation on various values
- error messages are more specific
- enforces that only one of UNTIL and COUNT may be present [disabled]
- allows lower-case property and enumeration values [disabled]
As part of the transition process, both versions of the parser are
called on every request, and the results are compared. If the results
are different a warning message is logged.
An unnecessary constructor was removed.
This also this moves some EventRecurrence tests out of CalendarProvider,
into coretests, and adds a simple parse test with the examples from
the RFC.
Bug 4575374
Change-Id: If737ed1272fda65c93363d87b2da12b85e644f5b
Engines must declare a <meta-data> attribute in their
manifest with name "android.speech.tts". This must reference
an XML resource as per
com.android.internal.R.styleable.TextToSpeechEngine.
Change-Id: I56a6b9f1a360174f98c9f39da901ade83d0f38a7
1. AccessibilityEvent was incorrectly setting the
connection of an owned AccessibilityRecord after
the record is initialized since during initialization
the record may become sealed.
bug:4724101
Change-Id: I39087dc8023c62252f31431ece23de901dc45972
Also:
. Cater for components that are GONE.
. Include code to draw component bounds and margins when in DEBUG mode.
Change-Id: I688f8b638469eb11987ebb207b7db1dc953e84e7
This change causes MultWaveView to look at historical motion events to make
unlocking easier during high system load.
Updated after review.
Change-Id: Ibfc3cb513936e3b8488aa4390164bf5e214c982f
- use a lazy padding resolution (because layout direction is lazyly resolved too)
- cache resolved layout direction as getResolvedLayoutDirection() will be more called
- enable resetting layout direction cache if needed
- update unit tests
Change-Id: I30ce19e3100cc137f84e60163b60e1577ff61819
And correctly upgrade NetworkIdentitySet written to disk, assuming
that old values aren't roaming.
Bug: 4724762
Change-Id: Ic25897ebbaf43be2390174d8e5fd08386bc8a345
