Please address the comments from this code review:

## Overall Comments
- Consider renaming IsAddToHead to a name like AddToHead or AppendToHead to better follow .NET boolean property naming conventions.
- Add disposal or parameter‐change logic to remove or update injected link tags when the component is unmounted or its parameters change to prevent stale entries.
- In the JavaScript init function, use the URL API (e.g. new URL(href, document.baseURI)) instead of string concatenation for more robust href comparisons and to support relative URLs.

## Individual Comments

### Comment 1
<location> `src/BootstrapBlazor/Components/HtmlTag/Link.razor.js:2-3` </location>
<code_context>
+export function init(options) {
+    const href = options.href;
+    const rel = options.rel;
+    const links = document.head.getElementsByTagName("link");
+    // 遍历所有link元素
</code_context>

<issue_to_address>
**issue:** Consider normalizing option property casing for consistency.

The C# object uses 'Href' and 'Rel', while the JS expects 'href' and 'rel'. Please align property names to prevent undefined values.
</issue_to_address>

### Comment 2
<location> `src/BootstrapBlazor/Components/HtmlTag/Link.razor.js:8` </location>
<code_context>
+    // 遍历所有link元素
+    for (let i = 0; i < links.length; i++) {
+        const hlink = links[i];
+        var nhref = hlink.baseURI + href;
+        if (hlink.href == nhref && hlink.rel == rel) {
+            return;
</code_context>

<issue_to_address>
**issue (bug_risk):** The construction of nhref may not match the actual href attribute value.

Directly concatenating baseURI and href can lead to incorrect URLs if href is absolute or already includes the base URI. Use proper URL resolution or compare hlink.href and href directly.
</issue_to_address>

### Comment 3
<location> `src/BootstrapBlazor/Components/HtmlTag/Link.razor.js:2` </location>
<code_context>
    const href = options.href;

</code_context>

<issue_to_address>
**suggestion (code-quality):** Prefer object destructuring when accessing and using properties. ([`use-object-destructuring`](https://docs.sourcery.ai/Reference/Rules-and-In-Line-Suggestions/JavaScript/Default-Rules/use-object-destructuring))

```suggestion
    const {href} = options;
```

<br/><details><summary>Explanation</summary>Object destructuring can often remove an unnecessary temporary reference, as well as making your code more succinct.

From the [Airbnb Javascript Style Guide](https://airbnb.io/javascript/#destructuring--object)
</details>
</issue_to_address>

### Comment 4
<location> `src/BootstrapBlazor/Components/HtmlTag/Link.razor.js:3` </location>
<code_context>
    const rel = options.rel;

</code_context>

<issue_to_address>
**suggestion (code-quality):** Prefer object destructuring when accessing and using properties. ([`use-object-destructuring`](https://docs.sourcery.ai/Reference/Rules-and-In-Line-Suggestions/JavaScript/Default-Rules/use-object-destructuring))

```suggestion
    const {rel} = options;
```

<br/><details><summary>Explanation</summary>Object destructuring can often remove an unnecessary temporary reference, as well as making your code more succinct.

From the [Airbnb Javascript Style Guide](https://airbnb.io/javascript/#destructuring--object)
</details>
</issue_to_address>

### Comment 5
<location> `src/BootstrapBlazor/Components/HtmlTag/Link.razor.js:8` </location>
<code_context>

</code_context>

<issue_to_address>
**issue (code-quality):** Use `const` or `let` instead of `var`. ([`avoid-using-var`](https://docs.sourcery.ai/Reference/Rules-and-In-Line-Suggestions/JavaScript/Default-Rules/avoid-using-var))

<details><summary>Explanation</summary>`const` is preferred as it ensures you cannot reassign references (which can lead to buggy and confusing code).
`let` may be used if you need to reassign references - it's preferred to `var` because it is block- rather than
function-scoped.

From the [Airbnb JavaScript Style Guide](https://airbnb.io/javascript/#references--prefer-const)
</details>
</issue_to_address>