From 9d5a70fc705590a490190e615238b52fd1e409dc Mon Sep 17 00:00:00 2001
From: BennyBPB <behr.benny@gmail.com>
Date: Sun, 18 Feb 2024 09:18:13 +0100
Subject: [PATCH 1/2] fix(spec-char-escape): remove normal ampersand from
 spec-char-escape rule, update test and docs

Ampersand is acceptable in HTML text. W3C Markup Validation Service no longer finds any issues with
the uncoded &.

fix #1382
---
 docs/user-guide/rules/spec-char-escape.md | 4 +++-
 src/core/rules/spec-char-escape.ts        | 2 +-
 test/rules/spec-char-escape.spec.js       | 9 +++------
 3 files changed, 7 insertions(+), 8 deletions(-)

diff --git a/docs/user-guide/rules/spec-char-escape.md b/docs/user-guide/rules/spec-char-escape.md
index b94658651..67ed84bcb 100644
--- a/docs/user-guide/rules/spec-char-escape.md
+++ b/docs/user-guide/rules/spec-char-escape.md
@@ -12,11 +12,13 @@ Level: `error`
 1. true: enable rule
 2. false: disable rule
 
-The following pattern are **not** considered violations:
+The following patterns are **not** considered violations:
 
 <!-- prettier-ignore -->
 ```html
 <span>aaa&gt;bbb&lt;ccc</span>
+<span>Steinway &amp; Sons, Q&amp;A</span>
+<span>Steinway & Sons, Q&A</span>
 ```
 
 The following pattern is considered violation:
diff --git a/src/core/rules/spec-char-escape.ts b/src/core/rules/spec-char-escape.ts
index de1601662..305657c41 100644
--- a/src/core/rules/spec-char-escape.ts
+++ b/src/core/rules/spec-char-escape.ts
@@ -7,7 +7,7 @@ export default {
     parser.addListener('text', (event) => {
       const raw = event.raw
       // TODO: improve use-cases for &
-      const reSpecChar = /([<>])|( \& )/g
+      const reSpecChar = /([<>])/g
       let match
 
       while ((match = reSpecChar.exec(raw))) {
diff --git a/test/rules/spec-char-escape.spec.js b/test/rules/spec-char-escape.spec.js
index b1f883537..cd8c5f674 100644
--- a/test/rules/spec-char-escape.spec.js
+++ b/test/rules/spec-char-escape.spec.js
@@ -21,13 +21,10 @@ describe(`Rules: ${ruleId}`, () => {
     expect(messages[2].col).toBe(4)
   })
 
-  it('Special characters: & should result in an error', () => {
-    const code = '<p>Steinway & Sons</p>'
+  it('Special characters: normal & should not result in an error', () => {
+    const code = '<p>Steinway & Sons Q&A</p>'
     const messages = HTMLHint.verify(code, ruleOptions)
-    expect(messages.length).toBe(1)
-    expect(messages[0].rule.id).toBe(ruleId)
-    expect(messages[0].line).toBe(1)
-    expect(messages[0].col).toBe(12)
+    expect(messages.length).toBe(0)
   })
 
   it('Normal text should not result in an error', () => {

From 3d893538ebdd4a5bbd61cd8063f688bb0ba8e785 Mon Sep 17 00:00:00 2001
From: BennyBPB <84272511+BennyBPB@users.noreply.github.com>
Date: Sun, 18 Feb 2024 11:39:21 +0100
Subject: [PATCH 2/2] Update spec-char-escape.ts

Remove fixed TODO comment.
---
 src/core/rules/spec-char-escape.ts | 1 -
 1 file changed, 1 deletion(-)

diff --git a/src/core/rules/spec-char-escape.ts b/src/core/rules/spec-char-escape.ts
index 305657c41..c436af9f8 100644
--- a/src/core/rules/spec-char-escape.ts
+++ b/src/core/rules/spec-char-escape.ts
@@ -6,7 +6,6 @@ export default {
   init(parser, reporter) {
     parser.addListener('text', (event) => {
       const raw = event.raw
-      // TODO: improve use-cases for &
       const reSpecChar = /([<>])/g
       let match