705d8c50fd
- App now shows how Angular handles untrusted URLs and resources - E2e test covered new functionality - Copyedits to prose - Updated provider expressions to use latest syntax The original security feature tracker: https://github.com/angular/angular/issues/8511
21 lines
742 B
HTML
21 lines
742 B
HTML
<!--#docregion -->
|
|
<h3>Bypass Security Component</h3>
|
|
|
|
<!--#docregion dangerous-url -->
|
|
<h4>A untrusted URL:</h4>
|
|
<p><a class="e2e-dangerous-url" [href]="dangerousUrl">Click me</a></p>
|
|
<h4>A trusted URL:</h4>
|
|
<p><a class="e2e-trusted-url" [href]="trustedUrl">Click me</a></p>
|
|
<!--#enddocregion dangerous-url -->
|
|
|
|
<!--#docregion iframe-videoid -->
|
|
<h4>Resource URL:</h4>
|
|
<p><label>Showing: <input (input)="updateVideoUrl($event.target.value)"></label></p>
|
|
<p>Trusted:</p>
|
|
<iframe class="e2e-iframe-trusted-src" width="640" height="390" [src]="videoUrl"></iframe>
|
|
<p>Untrusted:</p>
|
|
<iframe class="e2e-iframe-untrusted-src" width="640" height="390" [src]="dangerousVideoUrl"></iframe>
|
|
<!--#enddocregion iframe-videoid -->
|
|
|
|
<!--#enddocregion -->
|