Lines Matching refs:behavior

97   * Rule 27: Consistent inter-device behavior
132   * Rule 52: Consistent behavior after feature expansion
420 …tely defined, and the work should be completed according to the defined behavior in the correspond…
422 Unreliable behavior includes failure to return a value as scheduled or causing application exceptio…
517 * **Rule 27: Consistent inter-device behavior**
519 By default, an API should behavior the same between devices of different types.
521 If the behavior will be different because of the device types, clearly describe the differences and…
525 …ault, every API should provide consistent behavior in different versions. If an API change will ca…
527 Simply speaking, API behavior changes should not affect developed applications.
638 All code samples must be able to run properly. If the behavior of an API varies in different versio…
725 … locked or the application is switched to the background, stop the high power consumption behavior.
767 API deprecation and behavior changes greatly reduce maintenance efficiency of developers, especiall…
803 * **Rule 52: Consistent behavior after feature expansion**
807 It is important to keep API behavior consistent. The original behavior should not be damaged by the…
809 If the behavior has to be changed, only the applications using the new version provide the new beha…
813 …cument accordingly. From the perspective of compatibility, the original behavior should not be cha…
815 However, you can change the behavior of an existing API in the following cases:
846 * Defects related to API behavior: The behavior of an API is inconsistent with that described in th…
849 …may need to change the behavior of a published API. Note that behavior changes take effect only on…