docs: remove outdated refs to protocol.registerStandardSchemes (#17959)
This commit is contained in:
parent
075b818a8e
commit
e1acfffaf8
1 changed files with 1 additions and 4 deletions
|
@ -54,7 +54,6 @@ app.on('ready', () => {
|
||||||
})
|
})
|
||||||
})
|
})
|
||||||
```
|
```
|
||||||
Using `protocol.registerStandardSchemes` without the session will still register your custom protocol as a standard scheme.
|
|
||||||
|
|
||||||
## Methods
|
## Methods
|
||||||
|
|
||||||
|
@ -158,9 +157,7 @@ specified. For the available error numbers you can use, please see the
|
||||||
[net error list][net-error].
|
[net error list][net-error].
|
||||||
|
|
||||||
By default the `scheme` is treated like `http:`, which is parsed differently
|
By default the `scheme` is treated like `http:`, which is parsed differently
|
||||||
than protocols that follow the "generic URI syntax" like `file:`, so you
|
than protocols that follow the "generic URI syntax" like `file:`.
|
||||||
probably want to call `protocol.registerStandardSchemes` to have your scheme
|
|
||||||
treated as a standard scheme.
|
|
||||||
|
|
||||||
### `protocol.registerBufferProtocol(scheme, handler[, completion])`
|
### `protocol.registerBufferProtocol(scheme, handler[, completion])`
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue