Files

T

yeuimu 6c61a4e871 feat(deploy): production deployment setup and fixes

- Debian-based api image (bookworm-slim), docker/debian mirrors, prisma
  binaryTargets for openssl 3.0
- nginx: admin SPA under /admin, TLS via acme.sh (ZeroSSL) + auto-renewal
  cron, http->https redirect
- prisma: add origin_goods.delisted migration, sync missing schema
  (good_image/tag_font_color/good_tags), fix users.createdAt Timestamptz
- api: CORS wildcard reflection, helmet CORP cross-origin, price
  backfill in persistProductDetail, categoryIcon ancestor fallback,
  mediaByColor per-color gallery in public goods detail
- admin: /admin base path (vite + router)
- import-data.mjs: udt_name casting, serial sequence advance fix

2026-08-26 14:23:09 +08:00

2.8 KiB

Raw Blame History

title, impact, impactDescription, type, tags

title

impact

impactDescription

type

Event Modifier Order Matters

Impact: MEDIUM - When chaining event modifiers, the order determines behavior because Vue generates code in the same sequence. Using .prevent.self vs .self.prevent produces different results that can cause subtle bugs in event handling.

Task Checklist

Always consider modifier order when chaining multiple modifiers
Use .prevent.self to prevent default on element AND children
Use .self.prevent to prevent default ONLY on the element itself
Test event behavior on both the element and its children

Incorrect:

<!-- WRONG: Unintended behavior - prevents clicks on children too -->
<template>
  <div @click.prevent.self="handleClick">
    <button>Child Button</button> <!-- Default also prevented here! -->
  </div>
</template>

<!-- WRONG: Assuming order doesn't matter -->
<template>
  <!-- Developer expects only self clicks to be handled -->
  <!-- But .prevent runs first, affecting all clicks -->
  <a href="/page" @click.prevent.self="navigate">
    <span>Click me</span>
  </a>
</template>

Correct:

<!-- CORRECT: Only prevent default on the element itself -->
<template>
  <div @click.self.prevent="handleClick">
    <button>Child Button</button> <!-- Default NOT prevented here -->
  </div>
</template>

<!-- CORRECT: Prevent default on element and children -->
<template>
  <form @submit.prevent.self="onSubmit">
    <button type="submit">Submit</button>
  </form>
</template>

<!-- CORRECT: Explicit intent with separate handlers when needed -->
<template>
  <div @click.self="handleSelfClick">
    <button @click.prevent="handleChildClick">
      Child with prevented default
    </button>
  </div>
</template>

How Modifier Order Works

// Vue compiles modifiers in order, so:

// @click.prevent.self compiles to:
// event.preventDefault()
// if (event.target !== event.currentTarget) return
// handler()

// @click.self.prevent compiles to:
// if (event.target !== event.currentTarget) return
// event.preventDefault()
// handler()

Common Modifier Combinations

<!-- Stop propagation AND prevent default -->
<a @click.stop.prevent="handleClick">Link</a>

<!-- Capture mode with once -->
<div @click.capture.once="handleOnce">...</div>

<!-- Only exact modifier key combination -->
<button @click.ctrl.exact="onCtrlClick">Ctrl+Click Only</button>

Reference

Vue.js Event Handling - Event Modifiers

2.8 KiB Raw Blame History