Emmanuel

@liabru, yes, vieweing the live demo in Chrome (`Version 98.0.4758.102 (Official Build) (64-bit)`) does throw the warning, once per added body.

Sure thing! Heres a more complete user agent spec: ``` name: Chrome version: 98.0.4758.102 layout: Blink os: Windows 10 64-bit ``` Steps to reproduce: 1. Go to the [official demo...

I don't understand how > (with added types, to show verbosity) should be a valid part of the argument. If you are specifically looking for dependency "magic", isn't asserting every...

I'm currently designing the structure of a few composable components for a project and was wondering if this feature is still projected for `3.x` or if it is more likely...

Attempting to approach this in svelte 5 with svelte-kit 2 and the proposed alternative preprocessing doesn't seem to work as expected. If the preprocessor only declares the css layer component...

@techmunk, yes I am aware of the CSS spec, though without any particular reason I expected global stylesheets imported in script tags to be processed and inserted to the DOM...

@rodrigodagostino I'm fairly certain (but could be wrong though) that `a` tags with a non-empty href attribute (and non-`#`, that could be the source of the problem) are considered valid...

@rodrigodagostino I understand your points, but I feel you haven't read the issue description and its example rigorously. The problem is the inconsistency of the ~~errors~~ warnings contrasted to the...

@rodrigodagostino Fair points, I agree with your stance that, if we want to ensure a 100% identical behavior in terms of a11y, the one case standing out as invalid is...

While reading through https://github.com/sveltejs/rfcs/pull/60, I vaguely remember seeing someone mention some syntactic or compiler-imposed limitations that, from my understanding, currently block the ability to have things such as conditional events....