Match Rules For Isolating Visible Web Controls
I'm trying to match on an specific <LI> in a <UL>, here is what the list looks like:
The control i want is in red. The problem is that if the user navigates away from and then back to this page, when they next bring up this <UL> there are multiple controls that are getting matched. Here's the adapter matching details:
The visible control will have an entry in the Client Rectangle attribute, whereas the non-visible controls will have an ClientRectangle of 0,0,0,0, so I have added an attribute match rule using IsNotSimple (see above), yet the controls with this attribute still continue to be matched (also see above).
I'm trying to match on an specific <LI> in a <UL>, here is what the list looks like:
The control i want is in red. The problem is that if the user navigates away from and then back to this page, when they next bring up this <UL> there are multiple controls that are getting matched. Here's the adapter matching details:
The visible control will have an entry in the Client Rectangle attribute, whereas the non-visible controls will have an ClientRectangle of 0,0,0,0, so I have added an attribute match rule using IsNotSimple (see above), yet the controls with this attribute still continue to be matched (also see above).
So my request is for anyone who can help me update the match rules so that only the visible control is matched, and the 'hidded' ones are ignored, and to understand how the Attribute Match Rule works, as I have never been able to successfully use it.
Thanks.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
US
Can you provide the full outerhtml of the UL/LI element? and then if possible, another conflicting UL/LI control. I see you've matched to the SPAN element rather than the LI, is there a specific reason for that?
Tata Consultancy Services (TCS)
GB
Hi Mitchell,
The SPAN is lower down the path but there is no specific reason why I have used SPAN.
Here is the outerhtml for the visible LI control :
<li title="Identify Customer" class="menu-item menu-item-enabled" role="presentation"><a tabindex="-1" class="menu-item-anchor " role="menuitem" onclick="pd(event);" href="#" data-click='[["runScript", "pega.ui.HarnessActions.handleMenuAction(\"ActionChange62\",1,event,\"4\",\"SearchCustomerAutoSubmit\")"]]]' data-ctl="">
<span class="menu-item-title-wrap" data-click="."><span class="menu-item-title" data-click="..">Identify Customer</span></span></a></li>
Here is the outerhtml for non-visible control:
<li title="Identify Customer" class="menu-item menu-item-enabled" role="presentation"><a tabindex="-1" class="menu-item-anchor " role="menuitem" onclick="pd(event);" href="#" data-click='[["runScript",["pega.ui.HarnessActions.handleMenuAction(\"ActionChange62\",1,event,\"4\",\"SearchCustomerAutoSubmit\")"]]]' data-ctl=""><span class="menu-item-title-wrap" data-click="."><span class="menu-item-title" data-click="..">Identify Customer</span></span></a></li>
They look the same to me, hence why I am having to work with the other attributes available. Thanks