Passing a Browser Automation Handle

@mmirandanoriega

when you create a topic you can select feature request and it would be created as such and based on votes received product team would pick it up and update on thread

as of now with modern migration it is still not available to pass all options as well…but in a way that would restrict few things also…for example…in login you would use open always generally…but its not ideal for other pages…ifnotopen is also not ideal…so thats one reason they are kept separate…with object repository few options are being merged like the window selectors and input method etc but not all again…

now coming to reusables…think of it like this…when you build a reusable you build with a mindset that the component would be used again so building it would still help in other automations but yes we hear the concern of options needs to be choosen again but because of different requirements having few options left for choice is also a good way…the handle helps you with not passing url always, not selecting the window always as of now

Agree with you on limitations …the more we all give feedback the more it would be improved

one such feedback is this …Object Repository - Window Selector Change to sync to Elements

you can as well create

cheers

1 Like