hi - you seem to be reporting the details here exactly in reverse.
As we said previously, useNativeRadioItems has always affected the locator string - specifically, if it's false the locator will get a [Class=CheckboxItem]/valueicon, and if it's true, you'll get a [Class=RadioItem]/element, because those are the types that are used for radios.
This has always been the case. Depending on what kind of radios your skin had, you would get a different locator string. For example, in your previous version, if you had recorded a locator for a radoiItem in Stratus (which at that time had useNativeRadioItems: true), the locator would have been a Class=RadioItem one. If you record one today with the new build, it will have a Class=CheckboxItem.
The only change that's been made in this area is that, before, your Class=RadioItem locator would have failed to locate in a skin that uses Class=CheckboxItem - now, either of those locators will resolve in any skin.
Hi,
Yes you were right I reported in reverse order for skin issue and we are good with it now.
we have also fixed our code based on your input with Calendar issue.
Now we can close this topic.
I appreciate your quick response, detailed insights, and support.
Comment