svelte

Closes #18868. While hydrating, fills its cache from , which returns a string, and then compares it with the client value. A number or boolean never equals that string, so , , `data-selected={false}String(value)setAttributehrefxlink:hrefbackgroundclassidcodebaseformactionitemidlongdescmanifestusemaploaderrorvaluestableValueskernelMatrixtransformgradientTransformpatternTransformpointsxydxdyrotatebaseValbaseValattributeChangedCallbackdocument.createElement(localName)islocalNamenamespaceURIcreateElementObject.setPrototypeOf(el, HTMLButtonElement.prototype)mainset_attributessrcsrcsetmainsetAttributearia-rowindexcolspantabindexsvg widthheightstroke-widthsetAttributedata-selected={false}aria-hidden={true}translatedraggablewidthheightdisabledrequireddisabled={on}disabledruntime-browsermode: ['hydrate']MutationObserverbefore_testtesthydration/element-attribute-primitivesNaN1e21"1.0""-0""False"""toString{#if}runtime-browser/hydration-attribute-unchanged$effect.pre$effectlocalNamenamespaceURIdocument.createElementruntime-browser/hydration-attribute-writtentranslatedraggableisnamespaceURIlocalNameruntime-browser/hydration-attribute-realmsruntime-browser/hydration-attribute-recoverruntime-runes/async-hydration-attribute-unchanged{#if await ...}runtime-browserserver_propsmodefeat:fix:chore:docs:packages/svelte/srcnpx changesetpnpm testpnpm lint`

Before submitting the PR, please make sure you do the following [x] 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 [x] Prefix your PR title with , , , or . [x] This message body should clearly illustrate what problems it solves. [x] Ideally, include a test that fails without this PR but passes with it. [x] If this PR changes code within , add a changeset (). Tests and linting [ ] Run the tests with and lint the project with (full suites not run, ran targeted suites instead; see Tests below) Closes #16835. Problem: writing without on the script tag fails with a bare error, which sends people hunting in the wrong direction. Fix: when snippet parameter parsing fails as JavaScript, a conservative heuristic () inspects the raw params text. If it looks like TypeScript type annotations and the component has no , the error is augmented with: *Did you forget to add to your `{}[]a ? b : ctests/compiler-errors/samples/snippet-type-annotation-without-lang-tscompiler-errorsparser-modernparser-legacyvalidator(text: string)(text?: string)({a,b}: Props)({a: b})lang="ts"snapshotprops-identifier`) also fails on clean upstream main in my environment and is unrelated. Changeset added (patch).

Before submitting the PR, please make sure you do the following [x] 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 [x] Prefix your PR title with , , , or . [x] This message body should clearly illustrate what problems it solves. [x] Ideally, include a test that fails without this PR but passes with it. [x] If this PR changes code within , add a changeset (). Tests and linting [ ] Run the tests with and lint the project with (full monorepo runs not done; the three affected runtime suites plus eslint on the changed file were run, see Validation) Fixes #18070 Problem** With + mutating state that an turns into , the browser flushes effects at the microtask checkpoint between listeners mid-dispatch. The button is therefore already when the trusted click reaches the delegated at the root, and skipped the handler ( while is the inner `handle_event_propagationcurrent_target === handled_atevent[event_symbol]{@attach}$effectevent.isTrustedruntime-browserdelegated-onclick-mid-dispatch-disabled$effectreal_clickwindow.__real_clickonclick: 0onclick: 1domhydratecurrent_target === handled_atruntime-browserruntime-runesruntime-legacy_config.js` formatted with the repo's prettier settings