v-dialog persistent Prop: Detecting Blocked User-Initiated Close Attempts

Answers to your three questions

1. No. Vuetify's v-dialog does not document a separate event, callback, or prop that distinguishes a blocked user-initiated close attempt from a successful programmatic closure while persistent is enabled.
2. No. There is no officially recommended Vuetify pattern or plugin for detecting suppressed dismissal gestures on persistent dialogs.
3. The persistent prop was introduced in Vuetify 2. Available research indicates no user-gesture-detection change in Vuetify 3, but you should verify this against your installed major version because it affects the source path and workaround.

Confirmed behavior and likely explanation

Vuetify documents update:modelValue as the closure-related event for v-dialog. It fires for both user-initiated and programmatic closures and carries no metadata about the trigger or whether the dialog actually closed. The persistent prop is documented to block Escape key presses and clicks outside the dialog overlay.

The likely explanation is that Vuetify consumes the Escape keydown or overlay click internally when persistent is true, so the parent component never receives a distinct signal. Your application only sees update:modelValue, which cannot tell you whether the gesture was suppressed.

Steps for this case

1. Confirm your Vuetify major version:

npm ls vuetify

1. Track close intent at the application layer. Set a flag such as userRequestedClose in your own click or keyboard handler before updating v-model, rather than inferring intent from update:modelValue.
2. If you must detect the raw gesture, attach a global keydown listener for Escape or a click listener outside the dialog. This is fragile: it can fire before Vuetify consumes the event and may interfere with other components. Use it only as a temporary diagnostic.

Verification

Inspect the installed dialog source for the persistent guard:

grep -R "persistent" node_modules/vuetify/lib/components/v-dialog

Then run a minimal sandbox with persistent set to true, press Escape, and confirm that update:modelValue emits no extra payload identifying the gesture.

Missing diagnostic detail

Are you using Vuetify 2 or Vuetify 3? The version changes the source file to inspect and may affect the workaround, so confirming it will narrow the recommendation.

Assumptions and uncertainty

• This assumes a standard v-dialog without a custom wrapper or overridden close handler.
• Newer minor releases could add events not described here; check your installed version's changelog.
• Global listeners are not recommended for production because they are fragile and non-deterministic.