[
https://issues.apache.org/jira/browse/SLING-11205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17603096#comment-17603096
]
Joerg Hoh commented on SLING-11205:
-----------------------------------
https://github.com/apache/sling-org-apache-sling-testing-clients/pull/29 has
been merged and has made it into 3.0.14. But as [~tyge] has reported in
https://github.com/apache/sling-org-apache-sling-testing-clients/pull/30 the
patch is incomplete/buggy and provided a fix for it.
I am looking into it.
> Make SlingHttpResponse.getSlingLocation resilient to customizations
> -------------------------------------------------------------------
>
> Key: SLING-11205
> URL: https://issues.apache.org/jira/browse/SLING-11205
> Project: Sling
> Issue Type: Improvement
> Components: Apache Sling Testing Clients
> Affects Versions: Apache Sling Testing Clients 3.0.12
> Reporter: Abhinav Saraswat
> Assignee: Joerg Hoh
> Priority: Blocker
> Fix For: Apache Sling Testing Clients 3.0.16
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> SlingHttpResponse.getSlingLocation and other get methods should work when the
> HTML response is customised by adding things like class="" in order to test
> the customised application.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
