Wrong signature for WebKitEntriesCallback/WebKitErrorCallback/WebKitFileCallback
See original GitHub issueI was trying to override callback interface signature for WebKitEntriesCallback
/WebKitErrorCallback
/WebKitFileCallback
, added below json
in overridingTypes.json
:
{
"kind": "callback",
"interface": "WebKitEntriesCallback",
"signatures": [
"(entities: WebKitEntry[]): void"
]
},
{
"kind": "callback",
"interface": "WebKitErrorCallback",
"signatures": [
"(err: DOMError): void"
]
},
{
"kind": "callback",
"interface": "WebKitFileCallback",
"signatures": [
"(file: File): void"
]
}
based on .file() and .readEntries(). Related Typescript repo issue #18139
Then I changed baselines/dom.generated.d.ts
to:
interface WebKitEntriesCallback {
(entries: WebKitEntry[]): void;
}
interface WebKitErrorCallback {
(err: DOMError): void;
}
interface WebKitFileCallback {
(file: File): void;
}
But when I run ./build
to build and test, dom.generated.d.ts
is still the same, the snapshot test for it failed.
I am not familiar with F# here, is my json
input wrong in this case, or it is a bug from the build script?
eg: in browser.webidl.xml
, these callbacks defined as:
<callback-interfaces>
...
<interface name="WebKitEntriesCallback" extends="Object">
<methods>
<method name="handleEvent" type="void">
<param name="entries" type="WebKitEntry[]"/>
</method>
</methods>
</interface>
<interface name="WebKitErrorCallback" extends="Object">
<methods>
<method name="handleEvent" type="void">
<param name="err" type="DOMError"/>
</method>
</methods>
</interface>
<interface name="WebKitFileCallback" extends="Object">
<methods>
<method name="handleEvent" type="void">
<param name="file" type="File"/>
</method>
</methods>
</interface>
</callback-interfaces>
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
What does the "wrong signature type" SSL error means?
This error means that the TLS client (OpenSSL in updown.io case) is receiving a signature type which is considered invalid, and this happens...
Read more >sign - OpenSSL occasionally generates wrong signature
I have a C++ programme, ECDSA key pair and some string to sign. The programme generates signature and saves it ...
Read more >get.adobe.com results in wrong signature type #7126 - GitHub
So I'm understanding right, that each site uses SHA1 will produce tls12_check_peer_sigalg:wrong signature type error with openssl version >1.1.1 ...
Read more >ArmA 2 OA How to fix Wrong signature for file corepatch_a2.pbo
Today I'm showing you guys how to fix Wrong signature for file corepatch_a2.pbo!I also explain how to fix common "You were kicked off...
Read more >Error syncing the Rocky Linux channel due to wrong signature
After deep checking, it is found that some of the mirrors are having wrong signatures which prevents them from syncing suceessfully.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
(BTW, I think lib.d.ts should ultimately exclude all those nonstandard WebKit-specific types and require third-party definition files)
@saschanaz Nice 👍 Thanks for your help