Unable to identofy Salesforce Steelbrick's custom web-objects using xpath from developer tools
Reported by
rahulsin...@gmail.com,
Feb 7 2017
|
|||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36
Steps to reproduce the problem:
1. Login to SF and navigate to any existing quote page
2. click edit lines button to move to steelbrick's adding product page
3. try to identify steelbrick objects (those start with 'sb') from developer's tool using xpath
What is the expected behavior?
$x("//*[@id='mainButton'][text()=’Add Products’]") should have returned Add Products button from the page button error is thrown in chrome console
What went wrong?
Following is the error thrown :
Uncaught DOMException: Failed to execute '$x' on 'CommandLineAPI': The string '//*[@id='mainButton'][text()=’Add Products’]' is not a valid XPath expression.
at <anonymous>:1:1
(anonymous) @ VM7770:1
Did this work before? N/A
Chrome version: 56.0.2924.76 Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 24.0 r0
other objects of Salesforce (non-steelbrick) objects are easily identifiable on chrome BUT steelbrick objects are working as expected on firefox (xpath)
Attached a screenshot of the error
,
Feb 7 2017
DevTools just exposes Chrome builtin xpath implementation in console. Maybe root of issue is super old supported xpath spec version in Chrome - it's something like 1.x. Forwarded to xml component for further triage.
,
Feb 13 2017
,
Feb 13 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 12 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by nyerramilli@chromium.org
, Feb 7 2017