From 47715fd3062575dc2fd10d246f512eddb3e2c5a3 Mon Sep 17 00:00:00 2001
From: baseballyama <xydybaseball@gmail.com>
Date: Tue, 14 Nov 2023 21:20:43 +0900
Subject: [PATCH 1/3] update docs

---
 .../routes/docs/content/03-appendix/02-breaking-changes.md    | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/sites/svelte-5-preview/src/routes/docs/content/03-appendix/02-breaking-changes.md b/sites/svelte-5-preview/src/routes/docs/content/03-appendix/02-breaking-changes.md
index ce774f2b16..85b5acbc33 100644
--- a/sites/svelte-5-preview/src/routes/docs/content/03-appendix/02-breaking-changes.md
+++ b/sites/svelte-5-preview/src/routes/docs/content/03-appendix/02-breaking-changes.md
@@ -71,3 +71,7 @@ Previously Svelte would always insert the CSS hash last. This is no longer guara
 ### `contenteditable` behavior change
 
 If you have a `contenteditable` node with a corresponding binding _and_ a reactive value inside it (example: `<div contenteditable=true bind:textContent>count is {count}</div>`), then the value inside the contenteditable will not be updated by updates to `count` because the binding takes full control over the content immediately and it should only be updated through it.
+
+### `oneventname` attributes no longer accept string values
+
+In Svelte4, it was possible to specify HTML event attributes like `<button onclick="foo">`. However, this is no longer allowed in Svelte5.

From 15349e1cc49c308f0c15d79a65d454b85d497928 Mon Sep 17 00:00:00 2001
From: Simon H <5968653+dummdidumm@users.noreply.github.com>
Date: Tue, 14 Nov 2023 20:26:16 +0100
Subject: [PATCH 2/3] Update
 sites/svelte-5-preview/src/routes/docs/content/03-appendix/02-breaking-changes.md

Co-authored-by: Ben McCann <322311+benmccann@users.noreply.github.com>
---
 .../src/routes/docs/content/03-appendix/02-breaking-changes.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sites/svelte-5-preview/src/routes/docs/content/03-appendix/02-breaking-changes.md b/sites/svelte-5-preview/src/routes/docs/content/03-appendix/02-breaking-changes.md
index 85b5acbc33..3b598f43dd 100644
--- a/sites/svelte-5-preview/src/routes/docs/content/03-appendix/02-breaking-changes.md
+++ b/sites/svelte-5-preview/src/routes/docs/content/03-appendix/02-breaking-changes.md
@@ -74,4 +74,4 @@ If you have a `contenteditable` node with a corresponding binding _and_ a reacti
 
 ### `oneventname` attributes no longer accept string values
 
-In Svelte4, it was possible to specify HTML event attributes like `<button onclick="foo">`. However, this is no longer allowed in Svelte5.
+In Svelte 4, it was possible to specify HTML event attributes like `<button onclick="foo">`. However, this is no longer allowed in Svelte 5.

From fc429e0a293e31e848290fb2446cdf8379915568 Mon Sep 17 00:00:00 2001
From: Rich Harris <hello@rich-harris.dev>
Date: Tue, 14 Nov 2023 17:02:24 -0500
Subject: [PATCH 3/3] Update
 sites/svelte-5-preview/src/routes/docs/content/03-appendix/02-breaking-changes.md

---
 .../docs/content/03-appendix/02-breaking-changes.md       | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/sites/svelte-5-preview/src/routes/docs/content/03-appendix/02-breaking-changes.md b/sites/svelte-5-preview/src/routes/docs/content/03-appendix/02-breaking-changes.md
index 3b598f43dd..3841f36980 100644
--- a/sites/svelte-5-preview/src/routes/docs/content/03-appendix/02-breaking-changes.md
+++ b/sites/svelte-5-preview/src/routes/docs/content/03-appendix/02-breaking-changes.md
@@ -74,4 +74,10 @@ If you have a `contenteditable` node with a corresponding binding _and_ a reacti
 
 ### `oneventname` attributes no longer accept string values
 
-In Svelte 4, it was possible to specify HTML event attributes like `<button onclick="foo">`. However, this is no longer allowed in Svelte 5.
+In Svelte 4, it was possible to specify event attributes on HTML elements as a string:
+
+```svelte
+<button onclick="alert('hello')">...</button>
+```
+
+This is considered an anti-pattern and is no longer possible in Svelte 5, where properties like `onclick` replace `on:click` as the mechanism for adding [event handlers](/docs/event-handlers).