coen.bakker
Wallaby: Querying DOM element regardless of its visibility
I noticed that in the Wallaby.Query docs, under Query Options it says that the visible option “Determines if the query should return only visible elements (default: true ).”
I initially thought this meant that visible: false would match any visible or invisible element, since visible: true only matches visible elements. Using the option, however, it became clear visible: false matches invisible elements only.
Could it be an idea to have the option visibility that has values visible, invisible or any?
I often want to match elements regardless of whether they are visible or not. This would make that easier. Also, I have noticed that elements get hovered “spontaneously”, which may change their visibility unpredictably. That’s one reason why I don’t want to specify the visibility (true/false) when querying elements.
Most Liked
michallepicki
The type specifications say visible can be boolean() | :any - here’s the PR that added the :any option
coen.bakker
I am not moving the mouse programmatically when it happens.
My first guess was also that it had to do with the mouse position. I haven’t verified that, though.
Popular in Proposals: Ideas
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance










