You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the MultiSelectComponent, we noticed that it is wrapped inside a TouchableWithoutFeedback component. By default, the accessible attribute of the TouchableWithoutFeedback component is set to true, which prevents access to its internal elements on iOS through XCUITest. This makes it impossible for us to locate the internal elements during automated testing. Could we customize the accessible attribute on the TouchableWithoutFeedback component? Setting the accessible attribute to false would resolve this issue for us.
Description:
When using the
MultiSelectComponent
, we noticed that it is wrapped inside aTouchableWithoutFeedback
component. By default, theaccessible
attribute of theTouchableWithoutFeedback
component is set totrue
, which prevents access to its internal elements on iOS through XCUITest. This makes it impossible for us to locate the internal elements during automated testing. Could we customize theaccessible
attribute on theTouchableWithoutFeedback
component? Setting theaccessible
attribute tofalse
would resolve this issue for us.Code path:
react-native-element-dropdown -> src -> components -> MultiSelect -> index.tsx -> MultiSelectComponent -> _renderModal -> TouchableWithoutFeedback
The text was updated successfully, but these errors were encountered: