Skip to content

Conversation

@Khyati-Kapil
Copy link

docs(window): add userland example for detecting drag-stopped and resize-stopped events

This PR adds a userland JavaScript example demonstrating how developers can
detect when a window drag or resize operation has stopped by listening to
the continuously emitted tauri://move and tauri://resize events and
debouncing them.

Since native drag-end / resize-end events are not currently exposed by Tauri
and JS event detection is not reliable enough to be implemented in the
runtime, this example provides a recommended, practical solution for
developers needing this behavior.

The new section is added to learn/window-customization.mdx where other
window interaction examples (dragging, maximizing, custom titlebars) are
already documented.

@Khyati-Kapil Khyati-Kapil requested a review from a team as a code owner December 4, 2025 19:13
@github-project-automation github-project-automation bot moved this to 🪵 Backlog in Documentation Dec 4, 2025
@netlify
Copy link

netlify bot commented Dec 4, 2025

Deploy Preview for tauri-v2 ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 2a1d54c
🔍 Latest deploy log https://app.netlify.com/projects/tauri-v2/deploys/6931dd483d6d73000816e477
😎 Deploy Preview https://deploy-preview-3631--tauri-v2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 99 (🔴 down 1 from production)
Accessibility: 98 (no change from production)
Best Practices: 100 (no change from production)
SEO: 100 (no change from production)
PWA: 80 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@Legend-Master
Copy link
Contributor

Hey, thanks for working on this, but I'm not sure how useful is it to leave a very much incomplete solution like this, and by

I think this should be done on user land

I meant if a user wants to do it, they can, I don't mean we should document this in our guides, since those guides are meant to be the approaches we recommend

Sorry for being harsh on this, hope you understand 🙏

@Khyati-Kapil
Copy link
Author

Thank you for the clarification — that makes sense.

I misunderstood the original intention behind “should be done in userland”.
Totally understand your point about the guides reflecting recommended
approaches only. No worries at all — thanks for explaining it clearly.

If a more complete or reliable approach becomes possible in the future, I’d be
happy to revisit the idea in a way that aligns with Tauri’s recommendations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 🪵 Backlog

Development

Successfully merging this pull request may close these issues.

2 participants