Issue Station
Sign In
Tools hereToolbox

nextjs - 💡(How to fix) Fix HTML syntax errors when using new select element HTML syntax [3 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#84116•Fetched 2026-04-08 02:20:32
View on GitHub
Comments
3
Participants
2
Timeline
8
Reactions
1
Author
josepharharjosepharhar
Participants
icyJosephicyJosephjosepharharjosepharhar
Timeline (top)
commented ×3cross-referenced ×2issue_type_added ×1labeled ×1

Code Example

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.6.0: Mon Jul 14 11:28:30 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6030
  Available memory (MB): 36864
  Available CPU cores: 12
Binaries:
  Node: 24.8.0
  npm: 11.6.0
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.5.3 // Latest available version is detected (15.5.3).
  eslint-config-next: 15.5.3
  react: 19.1.0
  react-dom: 19.1.0
  typescript: 5.9.2
Next.js Config:
  output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/josepharhar/next-customizable-select-bug

To Reproduce

  1. Start the application in development
  2. Open in browser

Current vs. Expected behavior

There are errors about the HTML syntax which aren't up to date with recent browser changes which allow the select element to have arbitrary children:

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.6.0: Mon Jul 14 11:28:30 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6030
  Available memory (MB): 36864
  Available CPU cores: 12
Binaries:
  Node: 24.8.0
  npm: 11.6.0
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.5.3 // Latest available version is detected (15.5.3).
  eslint-config-next: 15.5.3
  react: 19.1.0
  react-dom: 19.1.0
  typescript: 5.9.2
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

No response

extent analysis

TL;DR

Update the Next.js configuration or the customizable select component to accommodate recent browser changes allowing arbitrary children in the select element.

Guidance

  • Review the HTML syntax in the customizable select component to ensure it aligns with the latest browser standards and updates, such as those described in the provided GitHub pull request and Mozilla documentation.
  • Check the Next.js version (currently 15.5.3) for any known issues or updates related to customizable select elements and HTML syntax compatibility.
  • Consider updating or modifying the customizable select component to use a library or approach that is compatible with the latest browser changes, as referenced in the Chrome blog post.
  • Verify that the issue persists after updating any relevant components or configurations to ensure the fix is effective.

Example

No specific code example can be provided without more details on the current implementation of the customizable select component.

Notes

The provided information suggests that the issue is related to HTML syntax compatibility with recent browser updates, but without more specific details on the implementation, it's challenging to provide a precise fix.

Recommendation

Apply a workaround by updating the customizable select component to align with the latest browser standards, as the issue seems to be related to compatibility rather than a specific version of Next.js that can be upgraded to fix the problem.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#API routing#API middleware#SSR setup#ISR setup#authentication setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING