chore: docs for the new fields from AccessibilityNodeInfo #862
Conversation
ankahanets
changed the title
README.md
Outdated
| @@ -222,6 +222,23 @@ bounds | The element's visible frame (`[left, top][right, bottom]`) | `[0,0][100 | |||
| displayed | Whether the element is visible to the user | 'true' | |||
| contentSize | The dimensions of the element's content area | `{"left": 0, "top":0, "width": 100, "height": 100, "scrollableOffset": 10, "touchPadding": 0}` | |||
| extras | The result of [getExtras](https://developer.android.com/reference/android/view/accessibility/AccessibilityNodeInfo#getExtras()). The value includes all key-value pairs as `key=value` separated by a semicolon (`;`). If the value is empty, then only key part ending with the equal sign will be present. | Part of extras in chrome browser:<br> `AccessibilityNodeInfo.roleDescription=;`<br>`AccessibilityNodeInfo.chromeRole=rootWebArea;`<br> `ACTION_ARGUMENT_HTML_ELEMENT_STRING_VALUES=`<br> `ARTICLE,BLOCKQUOTE,BUTTON,CHECKBOX` | |||
| a11y-important | Whether the element originates from a view considered important for accessibility | 'true' | |||
There was a problem hiding this comment.
Please also mention the minimum API level needed for corresponding properties to exist as well as the meaning of null values
There was a problem hiding this comment.
Actually, user can not receive null-value because in this case the field just will be absent.
There was a problem hiding this comment.
They could if they use getAttribute API rather than checking the page source.
Nevertheless it would be still useful to know why the particular field is missing from the XML output
|
Please also update package.json with the minimum server version supporting mentioned attributes |
Update package.json with the minimum server version supporting new properties
I've set |
yes, thanks |
mykola-mokhnach
changed the title
Related PR: appium/appium-uiautomator2-server#682