Bug 1744243 Comment 1 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Hi Marco.

I investigated the results of `HandlerService.exists()` with like the following code.
```
lazy.handlerService.exists(
  lazy.externalProtocolService.getProtocolHandlerInfo(scheme)
);
```
The results of comparison with `externalProtocolService.externalProtocolHandlerExists(scheme)` will be below.

| scheme | HandlerService.exists() | externalProtocolService.externalProtocolHandlerExists() 
|--------------|-----------|------------|
invalid | false | false | 
http | true | false |
https | true | false |
ftp | true | false |
about | false | false |
mailto | true | true |

From this result, it seems that we need to do something for `HandlerService.exists()` to use it.
For example, when initializing `URIFixup`, investigate whether or not we can trust `externalProtocolService.externalProtocolHandlerExists()`. Then if not trusted, get all protocol handler info from externalProtocolService somehow. Then we store them into `HandlerService`, we may be able to use.
What do you think?
Revision 1 by
on 
Hi Marco.

I investigated the results of `HandlerService.exists()` with like the following code.
```
lazy.handlerService.exists(
  lazy.externalProtocolService.getProtocolHandlerInfo(scheme)
);
```
The results of comparison with `externalProtocolService.externalProtocolHandlerExists(scheme)` will be below.

| scheme | HandlerService.exists() | externalProtocolService.externalProtocolHandlerExists() 
|--------------|-----------|------------|
invalid | false | false | 
http | true | false |
https | true | false |
ftp | true | false |
about | false | false |
mailto | true | true |

From this result, it seems that we need to do something for `HandlerService.exists()` to use it.
For example, when initializing `URIFixup`, investigate whether or not we can trust `externalProtocolService.externalProtocolHandlerExists()`. Then if not trusted, get all protocol handler info from externalProtocolService somehow. Then we store them into `HandlerService`, we may be able to use. 
But, if we do so, it seems that `HandlerService` may affect other places as well, and I think that we can manage it here without using `HandlerService`.
What do you think?
Revision 2 by
on 
Hi Marco.

I investigated the results of `HandlerService.exists()` with like the following code.
```
lazy.handlerService.exists(
  lazy.externalProtocolService.getProtocolHandlerInfo(scheme)
);
```
The results of comparison with `externalProtocolService.externalProtocolHandlerExists(scheme)` is below.

| scheme | HandlerService.exists() | externalProtocolService.externalProtocolHandlerExists() 
|--------------|-----------|------------|
invalid | false | false | 
http | true | false |
https | true | false |
ftp | true | false |
about | false | false |
mailto | true | true |

From this result, it seems that we need to do something for `HandlerService.exists()` to use it.
For example, when initializing `URIFixup`, investigate whether or not we can trust `externalProtocolService.externalProtocolHandlerExists()`. Then if not trusted, get all protocol handler info from externalProtocolService somehow. Then we store them into `HandlerService`, we may be able to use. 
But, if we do so, it seems that `HandlerService` may affect other places as well, and I think that we can manage it here without using `HandlerService`.
What do you think?

Back to Bug 1744243 Comment 1