MVP keywords

Look at existing SeleniumLibrary keywords and figure out how to prioritize implementing them. Maybe create different tiers like “must have, nice to have, not a priority” or something like that.

Edit: added Tatu’s list to this post for easier Kanban tracking

• #50 Select from List keyword
• Deselect from list (Might need to be programmed as custom JS)
• #54 Frame support. No idea how Playwright supports it, but it gets asked pretty often in SL side. Selecting frames and deselecting, no need to implement mistakes done in SL side tough.
• #42 Support for opening multiple browsers/context/page
  • Try out solutions like Switch Context or using Open Browser to create new contexts - ask user input before committing to a technical solution
  • Switch Browser alias_or_index
  • New Browser, New Context and New Page
• Support for toggling check boxes and getting checkbox values.
• Input Password Same as input text but without any logging anywhere in any level.

Rene’s Feature requests:

• Type Text Fill Text Instead added a parameter to input text to toggle typing / filling
• Press Key added Press Keys selector *keys
• Wait until Element is condition selector (condition could be clickable, unclickable, visible, invisible, enabled, disabled)

[Snooz82]

A list of Keyword i would like to see.

Open Browser   url=None   browser=chromium   alias=None   options=None
Close Browser
Go To      url
Get Url

Click Element    selector

Type Text    selector    text
Fill Text    selector     text

Get Text    selector
Get Attribute     selector

Press Key    selector    key

Select Options    selector    *options
 
Wait until Element is     condition    selector     (condition could be clickable, unclickable, visible, invisible, enabled, disabled)
   
Switch Browser    alias_or_index

[xylix]

Closed in favour of #54 and #42