Skip to content

Conversation

@Rich-Harris
Copy link
Member

Another XHTML thing, per #17418 (comment) (that PR doesn't address this issue)

Before submitting the PR, please make sure you do the following

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • Prefix your PR title with feat:, fix:, chore:, or docs:.
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.
  • If this PR changes code within packages/svelte/src, add a changeset (npx changeset).

Tests and linting

  • Run the tests with pnpm test and lint the project with pnpm lint

@changeset-bot
Copy link

changeset-bot bot commented Feb 9, 2026

🦋 Changeset detected

Latest commit: 18f4c13

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
svelte Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@Rich-Harris Rich-Harris temporarily deployed to Publish pkg.pr.new (maintainers) February 9, 2026 19:42 — with GitHub Actions Inactive
@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2026

Playground

pnpm add https://pkg.pr.new/svelte@17664

@svelte-docs-bot
Copy link

@7nik
Copy link
Contributor

7nik commented Feb 10, 2026

I fact I mentioned this one in the discord:

In XHTML tag names must be lowercased.
Also, XHTML attributes must be lowercased as well to work - not sure what to do here.

I doubt we really need it and I'm agree with @paulocoghi about leaving the lowercasing in XHTML to the user's responsibility

you know if you are writing XHTML and if you purposefully write code that doesn't adhere with what you are serving and expect svelte to correct that screw you 😄


In the #17418 (comment) I meant the runtime check, which that PR address but incorrecly because <iNpUt> won't be rendred and behave as the input in XHTML, only <input>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants