Iakiv Kramarenko

These commits were already made in context of this feature: Oct 24, 2024 [NEW: appium device support (POC)](https://github.com/yashaka/selene/commit/a6b1bd46520ad0e93b3c5fd8df2e61e2e97e2f68) Oct 24, 2024 [REFACTOR: device platform-processing to be more lazy](https://github.com/yashaka/selene/commit/047376d291c1ad298f61ed58a583e248e5122a8c) Jan 29,...

Here goes the discussion [happened in Selene chat](https://t.me/selene_py_ru/25667). --------------------------- _Yasha, [31.01.2025 17:31]_ 💡 Hey everyone! I’ve slowly started setting aside time to prepare for the next release again. And I’d...

Hm... yet we can achieve same via `have.css_class('.*errorMessage.*').pattern` or even `have.css_class('*errorMessage*').with_wildcards` that can be implemented in #537

@cachebag Seems like you are right... We can keep `be._empty` still marked as experimental with `_` prefix, just in case somebody else will find other arguments... In meantime it seems...

yes, make sense... but probably it's good to add this test together with a refactored implementation...

@Kkevingo, Unfortunately, right now is not the best time to implement this... Because I am in the middle of big refactoring that will affect also this feature... We have to...

Oh... Seems like it's better to wait for this refactoring to be finished... I have quickly reviewed first 50 issues and have not found any suitable to delegate to you...

hm... Good question... Seems like I have used some kind of Ok-workaround for such cases in the past... But can't recall which... I will try to recall... I will also...

Yes, my proposed workaround is pretty awkward:) I also don't practice storing selectors separately... Yet, there should be a better way to implement what you want (wihtout additional wait_until_one_of_visible) logic....

Seems like the answer is: "Yes" According to 45 answers in [this](https://t.me/selene_py_ru/25685) poll.