docs(README): Clarify why Chrome-only methods have no Promise (#183)
This commit is contained in:
parent
3aad2418d8
commit
6fb04ebc66
|
@ -284,8 +284,11 @@ This library takes its knowledge of the APIs to wrap and their signatures from a
|
||||||
If an API method is not yet included in this "API metadata" file, it will not be recognized.
|
If an API method is not yet included in this "API metadata" file, it will not be recognized.
|
||||||
Promises are not supported for unrecognized APIs, and callbacks have to be used for them.
|
Promises are not supported for unrecognized APIs, and callbacks have to be used for them.
|
||||||
|
|
||||||
File an issue in this repository for API methods that supports a callback on Chrome and
|
Chrome-only APIs have no promise version, because extensions that use such APIs
|
||||||
are currently missing from the "API metadata" file.
|
would not be compatible with Firefox.
|
||||||
|
|
||||||
|
File an issue in this repository for API methods that support callbacks in Chrome *and*
|
||||||
|
Firefox but are currently missing from the "API metadata" file.
|
||||||
|
|
||||||
### Issues that happen only when running on Firefox
|
### Issues that happen only when running on Firefox
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue