foo-webview-sdk
    Preparing search index...

    Interface DndGetCapabilitiesSuccess

    Successful response from dnd.getCapabilities.

    interface DndGetCapabilitiesSuccess {
        dragOut: boolean;
        dragOutUnavailableReason?:
            | "register-failed"
            | "not-visual-hosting"
            | "runtime-too-old";
        hosting: "standard"
        | "visual";
        html5: boolean;
        paths: boolean;
        pathsUnavailableReason?:
            | "register-failed"
            | "forward-unavailable"
            | "inner-target-not-found"
            | "chain-failed"
            | "origin-untrusted";
        success: true;
    }
    Index
    dragOut dragOutUnavailableReason? hosting html5 paths pathsUnavailableReason? success
    dragOut: boolean

    Files can be dragged out of the window through dnd.prepareDrag. Independent of paths.

    dragOutUnavailableReason?:
        | "register-failed"
        | "not-visual-hosting"
        | "runtime-too-old"

    Why dragOut is false; its presence always means dragOut is false.

    hosting: "standard" | "visual"

    How the window hosts its WebView: visual for the main and popup windows, standard for a DUI or CUI panel.

    html5: boolean

    The page receives standard HTML5 drag events; false means the window has no drag-drop support at all.

    paths: boolean

    Real filesystem paths are obtainable through dnd.getPathsAsync and the dnd:* events. Not fixed for the window's lifetime: a navigation or Chromium re-registering its own drop target can withdraw it, announced by dnd:capabilitiesChanged.

    pathsUnavailableReason?:
        | "register-failed"
        | "forward-unavailable"
        | "inner-target-not-found"
        | "chain-failed"
        | "origin-untrusted"

    Why paths is false; its presence always means paths is false.

    success: true

    Always true here; a failed call resolves with ApiFailure instead.

    Settings
    Member Visibility

    On This Page
    Properties