feat: expose wry permission handler API in tauri#14865
Open
F0RLE wants to merge 4 commits into
Open
Conversation
Contributor
Package Changes Through 5662578There are 9 changes which include tauri with minor, @tauri-apps/cli with minor, tauri-cli with minor, tauri-utils with patch, tauri-build with patch, tauri-macos-sign with patch, tauri-bundler with minor, tauri-runtime-wry with minor, tauri-runtime with minor Planned Package VersionsThe following package releases are the planned based on the context of changes in this pull request.
Add another change file through the GitHub UI by following this link. Read about change files or the docs at github.com/jbolda/covector |
F0RLE
force-pushed
the
feat/permission-handler
branch
from
5662578 to
3a3f629
Compare
Exposes the with_permission_handler API from wry through Tauri's public interface, allowing Tauri applications to programmatically handle webview permission requests. New public types in auri-runtime: - PermissionKind - 17 variants matching wry's API, with Hash and Display. Display uses kebab-case (e.g. display-capture, pointer-lock). - PermissionResponse - Allow, Deny, Default (default), Prompt. With Hash. WebviewBuilder::on_permission_request accepts a closure called whenever the webview requests a browser permission (media, geolocation, etc.). Platform support mirrors wry: - Windows (WebView2): Full coverage of all 12 permission kinds. - macOS / iOS (WKWebView): Camera and microphone, secure Default behavior. - Linux (WebKitGTK): UserMedia, Geolocation, Notifications, PointerLock. DisplayCapture fallback for WebKitGTK < 2.42. - Android: Experimental support via JNI bridge. Signed-off-by: F0RLE <lrshka.klim7766@gmail.com>
F0RLE
force-pushed
the
feat/permission-handler
branch
2 times, most recently
from
bec30a9 to
832652b
Compare
F0RLE
force-pushed
the
feat/permission-handler
branch
from
832652b to
940e9c4
Compare
# Conflicts: # crates/tauri-runtime-wry/Cargo.toml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR exposes the expanded
wryPermission Handler API through Tauri, allowing applications and plugins to intercept, manage, and respond to WebView permission requests across supported backends.It wires the permission handler through
tauri-runtime,tauri-runtime-wry, Tauri core builders, individual webviews, and the plugin system. Until the matchingwrychanges are released,tauri-runtime-wrypoints at the correspondingwryPR revision.Key Changes
PermissionKindandPermissionResponsetypes totauri-runtimeandtauri-runtime-wry, mirroringwry's permission API. The permission kinds includeDisplayCapture,Midi,Sensors,MediaKeySystemAccess,LocalFonts,WindowManagement,PointerLock,AutomaticDownloads,FileSystemAccess, andAutoplay.on_permission_requesttotauri::Builder, allowing applications to intercept permission requests globally for all webviews.on_permission_requesttotauri::webview::WebviewBuilderandtauri::window::WebviewWindowBuilder, providing granular control for specific webviews/windows.on_permission_requestcallback to thePlugintrait andtauri::plugin::Builder, allowing plugins to handle permission requests for their own domain when the application does not override them.Permission Resolution Order
Incoming permission requests now flow through a clear hierarchy:
on_permission_request.Default(or has no handler), the globaltauri::Builderhandler evaluates the request.Default, the request iterates through registered plugins viaPluginStore::on_permission_request.Default, the underlyingwryimplementation falls back to the native backend behavior.