Selene

Latest version: v1.0.2

Safety actively analyzes 636221 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 5 of 16

2.0.0b5

- NEW: added command.js.*:
- remove
- set_style_display_to_none
- set_style_display_to_block
- set_style_visibility_to_hidden
- set_style_visibility_to_visible
Example:

browser.all('[id^=google_ads]').perform(command.js.remove)

2.0.0b4

- NEW: upgrade selenium to 4.2.0 & webdriver-manager to 3.7.0
- FIX: set_window_size in shared.browser.open
- FIX: provide correct chrome type for wdm

2.0.0b3

- added support of python 3.10.* [393](https://github.com/yashaka/selene/issues/393)
- upgraded webdriver-manager to 3.5.4 [408](https://github.com/yashaka/selene/issues/393)

2.0.0b2

- first steps on simplifying the current browser management,
yet making it more powerful
- now you can pass a lambda to `browser.config.driver = HERE`
providing more smart logic of driver management
see a dummy example at this [test](https://github.com/yashaka/selene/tree/master/tests/acceptance/custom_driver_source/test_adding_todos.py)

2.0.0b1

- added support selenium 4.1 [375](https://github.com/yashaka/selene/issues/375)
- the =4.1 version is frozen/hardcoded as dependency
- without backwards compatibility to selenium 3
- the newly added service arg have been added to automatic driver management on the selene side
- yet, if anyone needs backwards compatibility, we can consider implementing it in following patches, feel free to file an issue;)
- fixed [398](https://github.com/yashaka/selene/issues/398)
- Upgrade [webdriver-manager](https://github.com/SergeyPirogov/webdriver_manager) 3.5.0 -> 3.5.3 ([see changes](https://github.com/SergeyPirogov/webdriver_manager/compare/v3.5.0...v.3.5.3))
- removed deprecation
- from:
- collection.should_each(element_condition)
- reason:
- making collection.should(condition) so smart that it can accept both collection_condition and element_condition might be not a good idea – it violates KISS
- maybe keeping things simpler with extra method like should_each is better...
- let's see...
- element.send_keys(keys)
- reason:
- yes, send_keys is low level, but sometimes somebody needs this low level style, because of the nature and context of send_keys usage, like sending keys to hidden fields
- yet not sure about this decision... let's see...

2.0.0a40

- added `browser.config.wait_for_no_overlap_found_by_js` (`False` by default)
- making following element methods to wait for no overlap:
- type(text)
- set_value(value)
- press(*keys)
- clear()
- submit()
- double_click()
- btw normal `.click()` does not need it because have such waiting built in
- context_click()
- hover()

Page 5 of 16

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.