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
{{ message }}
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.
At the moment, by.model matches input elements with ng-model, but nothing else using ng-model. It makes more sense semantically to match anything. The potential downside is that if you have an input and (e.g.) select with the same model, by.model becomes ambiguous. Is this an important distinction for anyone?
The text was updated successfully, but these errors were encountered:
Is there a way to narrow the scope of the selector? I seem to recall using from karma which would select a subset of the dom for the input selectors to match within.
element(by.model('mymodel')).getText() for a textarea returns empty string whereas
element(by.model('mymodel')).getAttribute('value') returns the text inside a textarea.
why is that?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
At the moment,
by.model
matchesinput
elements withng-model
, but nothing else usingng-model
. It makes more sense semantically to match anything. The potential downside is that if you have an input and (e.g.) select with the same model,by.model
becomes ambiguous. Is this an important distinction for anyone?The text was updated successfully, but these errors were encountered: