Typescript: Missing WebKitEntry in dom lib with next version

[akosyakov]

Config:

{
    "compilerOptions": {
        "skipLibCheck": true,
        "declaration": true,
        "declarationMap": true,
        "noImplicitAny": true,
        "noEmitOnError": false,
        "noImplicitThis": true,
        "noUnusedLocals": true,
        "strictNullChecks": true,
        "experimentalDecorators": true,
        "emitDecoratorMetadata": true,
        "downlevelIteration": true,
        "module": "commonjs",
        "moduleResolution": "node",
        "target": "es5",
        "jsx": "react",
        "lib": [
            "es6",
            "dom"
        ],
        "sourceMap": true
    }
}

[RyanCavanaugh]

Dupe of #18139? It's really hard to tell.

To expedite the triage process, we need everyone to follow the issue template and instructions.

When you clicked "Create New Issue", the issue form was pre-populated with a template and some instructions. We need you to read those instructions completely, follow them, and then fill in all the fields in that template.

[akosyakov]

@RyanCavanaugh I've seen #18139, but it does not sound like my issue. https://github.com/theia-ide/theia/blob/1e3f8dbb0915cc8ee2f47ddffa1f7e597cb3f992/packages/filesystem/src/browser/file-tree/file-tree-model.ts#L153 compiles with 2.9.2, but does not compile with next. WebKitEntry is missing at all.

[mhegazy]

We have moved to generate the lib.d.ts from the webidl spec instead of from the Edge webidl spec. the result of that is many vendor speciifc declarations are removed and only declarations part of the spec are left behind. TS 3.0 will bring some of these changes, and TS 3.1 will bring the rest. this includes things like:

• WebKitEntriesCallback
• WebKitErrorCallback
• WebKitFileCallback
• WebKitDirectoryEntry
• WebKitDirectoryReader
• WebKitEntry
• WebKitFileEntry
• WebKitFileSystem
• MSAccountInfo
• MSAudioLocalClientEvent
• MSAudioRecvPayload
• MSAudioRecvSignal
• MSAudioSendPayload
• MSAudioSendSignal
• MSConnectivity
• MSCredentialFilter
• MSCredentialParameters
• MSCredentialSpec
• MSDCCEventInit
• MSDSHEventInit
• CanvasRenderingContext2D.mozImageSmoothingEnabled
• CanvasRenderingContext2D.oImageSmoothingEnabled
• CanvasRenderingContext2D.webkitImageSmoothingEnabled
• CanvasRenderingContext2D.msFillRule
• etc..

The recommendation for the vendor specific properties is to define in them locally in a .d.ts file.

[typescript-bot]

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.

[richard457]

Hello, I can see you have removed webkit from API, how to work around it for existing project that depends on it? seems adding them in lib.d.ts does not solve a problem.