A developer has a component named foobar with the following file: FooBar.java
foobar.html
What is the output when this component is rendered?
A.
B.
C.
D.
|
Download Printable PDF. VALID exam to help you PASS. |
 |
A developer has a component named foobar with the following file: FooBar.java
foobar.html
What is the output when this component is rendered?
A.
B.
C.
D.
|
Download Printable PDF. VALID exam to help you PASS. |
|
I believe the answer is C
https://experienceleague.adobe.com/docs/experience-manager-htl/using/getting-started/getting-started.html?lang=en#common-patterns-with-htl
All answers are wrong =/
It’s all about using the Context of the HTL .
By default for an attribute href uses context=uri. It validate provided URL and shouldn’t show anything in this case. Thus all answers here are incorrect.
Another problem is that by default for attributes uses context=attribute. And accordingly to Adobe docs in this case all special characters must be encoded. Therefore, in our case we have to see title=”foo%27bar”. But my browser displays title=”foo’bar”
¯\_(ツ)_/¯
foor’bar
after using context=’uri’
${customhtl.string}
foor’bar
${properties.jcr:title @ context=’uri’}
${customhtl.string}
foor’bar
A
What’s the correct answer?
A
whats correct answer
The aptest answer is D.
While rendering it takes care of rendering the exact quote on the browser. However the link checker will prevent the loading of an invalid link. So the options are ultimately incorrect.
single quote in ASCII CODE id '