Bug with select step - original design of containing value fail for edge cases

[kensoh]

In tagui_header.js, the following line

if (!found && opt.value.indexOf(valueToMatch) !== -1)

has to be changed to the following

if (!found && opt.value == valueToMatch)

The original design was to match when the option contains the value provided. But this loose definition clearly now encounters an edge case where the values are '-1', '0', '1', '2', '3'..

Providing '1' as value would match with '-1' since '-1' contains '1'). Making this change may cause some existing user scripts to fail (assuming that the search is based on contains).

But is necessary change, otherwise, there is no way to click on the option with '1', as first spotted in this edge case - tebelorg/RPA-Python#71

[kensoh]

Bug fixed with above commit. Fix now available in cutting edge version -

https://github.com/kelaberetiv/TagUI#set-up