| Index: LayoutTests/navigatorcontentutils/is-protocol-handler-registered-expected.txt
|
| diff --git a/LayoutTests/navigatorcontentutils/is-protocol-handler-registered-expected.txt b/LayoutTests/navigatorcontentutils/is-protocol-handler-registered-expected.txt
|
| index a1a60ee518d234f4c209d0e5bae4a7e21b69e282..482a876bc47954fa1d4cb8855b29438ae6ae00a1 100644
|
| --- a/LayoutTests/navigatorcontentutils/is-protocol-handler-registered-expected.txt
|
| +++ b/LayoutTests/navigatorcontentutils/is-protocol-handler-registered-expected.txt
|
| @@ -6,6 +6,7 @@ PASS Invalid scheme "mailto:" falied.
|
| PASS Invalid scheme "ssh:/" falied.
|
| PASS Invalid scheme "magnet:+" falied.
|
| PASS Invalid scheme "tel:sip" falied.
|
| +PASS Invalid url threw SecurityError exception: "Failed to execute 'isProtocolHandlerRegistered' on 'Navigator': Can only register custom handler in the document's origin.".
|
|
|
| Check if isProtocolHandlerRegistered() works correctly. If isProtocolHandlerRegistered() returns 'new' state, it works well.
|
| 'bitcoin' protocol will be registered, and then checks if the 'bitcoin' protocol is registered by isProtocolHandlerRegistered().
|
|
|