diff --git a/site/content/docs/02-template-syntax.md b/site/content/docs/02-template-syntax.md
index 070dc46687..11f59e3edc 100644
--- a/site/content/docs/02-template-syntax.md
+++ b/site/content/docs/02-template-syntax.md
@@ -545,6 +545,26 @@ Numeric input values are coerced; even though `input.value` is a string as far a
 ```
 
 
+##### A gotcha when using `on:` and `bind:` together
+
+Note that if you add an event handler and bind a property, they will be executed in the order you write them in the template.
+
+---
+
+For example, here `onChange` will be attached (and called) before the internal event handler added by `bind:value`.
+
+```sv
+<input type="number" on:change={onChange} bind:value>
+```
+
+---
+
+In the opposite case, if `bind:value` is before `on:change` then your change handler will see the updated bound value.
+
+```sv
+<input type="number" bind:value on:change={onChange}>
+```
+
 ##### Binding `<select>` value
 
 ---
diff --git a/site/content/examples/05-bindings/11-component-bindings/meta.json b/site/content/examples/05-bindings/11-component-bindings/meta.json
index 4c921d0e8a..5ed7f96ac2 100644
--- a/site/content/examples/05-bindings/11-component-bindings/meta.json
+++ b/site/content/examples/05-bindings/11-component-bindings/meta.json
@@ -1,3 +1,3 @@
 {
 	"title": "Component bindings"
-}
\ No newline at end of file
+}
diff --git a/site/content/examples/05-bindings/12-binding-gotcha/App.svelte b/site/content/examples/05-bindings/12-binding-gotcha/App.svelte
new file mode 100644
index 0000000000..66902f99c7
--- /dev/null
+++ b/site/content/examples/05-bindings/12-binding-gotcha/App.svelte
@@ -0,0 +1,63 @@
+<script>
+	const items = [{ name: 'A', val: 1 }, { name: 'B', val: 2 }];
+	const selected = {...items[0]};
+
+	function change() {
+		items.forEach(item => {
+			if (item.name === selected.name) {
+				selected.val = item.val;
+			}
+		});
+	}
+</script>
+
+<h3>Order between <code>bind:</code> and <code>on:</code> matters</h3>
+
+<p>if you add an event handler and bind a property, they will be executed in the order you write them in the template.</p>
+
+<h4>✅ Binding first</h4>
+<select
+	bind:value={selected.name}
+	on:change={change}
+
+>
+	{#each items as item}
+		<option value={item.name}>{item.val}</option>
+	{/each}
+</select>
+
+<p><span class="ok">This dropdown works as expected</span> because <code>bind:value</code> is before <code>on:change</code> so that your change handler sees the updated bound value.</p>
+
+<h4>❗️ Event handler first</h4>
+<select
+	on:change={change}
+  bind:value={selected.name}
+>
+	{#each items as item}
+		<option value={item.name}>{item.val}</option>
+	{/each}
+</select>
+
+<p><span class="gotcha">This dropdown won't work</span> (*) because by placing the <code>on:change</code> before the <code>bind:value</code> your event handler gets attached (and called) before the internal event handler added by <code>bind:value</code>.</p>
+
+<p class="note">(*) On Firefox both the dropdown and the selected value the won't update. On Chrome, the dropdown updates but the selected value won't.</p>
+
+<h4>Selected value</h4>
+<input bind:value={selected.val}>
+
+<style>
+	p {
+		line-height: 1.5rem
+	}
+
+	code {
+		background-color: lavender;
+		padding: 0.2rem;
+		font-size: 1.1rem;
+	}
+
+	.note {
+		font-style: italic;
+		font-size: 0.8rem;
+	}
+</style>
diff --git a/site/content/examples/05-bindings/12-binding-gotcha/meta.json b/site/content/examples/05-bindings/12-binding-gotcha/meta.json
new file mode 100644
index 0000000000..fd0c67e609
--- /dev/null
+++ b/site/content/examples/05-bindings/12-binding-gotcha/meta.json
@@ -0,0 +1,3 @@
+{
+	"title": "Binding gotcha"
+}
diff --git a/site/static/examples/thumbnails/binding-gotcha.jpg b/site/static/examples/thumbnails/binding-gotcha.jpg
new file mode 100644
index 0000000000..415ac3d2a7
Binary files /dev/null and b/site/static/examples/thumbnails/binding-gotcha.jpg differ