[
https://issues.apache.org/jira/browse/TAP5-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18055631#comment-18055631
]
ASF subversion and git services commented on TAP5-2816:
-------------------------------------------------------
Commit 6ff6ded4047f55d7a5fd3b6027a500e04015a140 in tapestry-5's branch
refs/heads/master from Ben Weidig
[ https://gitbox.apache.org/repos/asf?p=tapestry-5.git;h=6ff6ded40 ]
TAP5-2816: SeleniumTestCase replace By.link with By.xpath locator
> Selenium By.link might fail due to security manager veto
> --------------------------------------------------------
>
> Key: TAP5-2816
> URL: https://issues.apache.org/jira/browse/TAP5-2816
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-test
> Affects Versions: 5.10.0
> Reporter: Ben Weidig
> Assignee: Ben Weidig
> Priority: Major
>
> The integration tests use a {{By.link}} locator to click on links.
> Selenium 4.12 uses a JavaScript "atom" to execute {{By.linkText}} by
> iterating over {{document.links}} and reading the 'text' property.
> Depending on the Firefox version and profile, the XPConnect Security Manager
> might veto this script.
> To fix this, we should use browser native selectors (XPath or CSS), as
> Selenium uses them directly, not via JS.
> This will require a few adaptions in tests (e.g. case-senstivitiy of the link
> text).
> This might break code of people using SeleniumTestCase for their own tests as
> a base, but it should be easy to adapt the tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
