On Wed, Nov 20, 2024 at 9:25 AM Alex Russell <slightly...@chromium.org> wrote:
> In future, I'd like to see the TAG push back on things like Import Maps > and Speculation Rules that use `<script type="...">` as a semantic black > box. These features need to: > > - Compose consistently, or at least sanely (as this Intent proposes) > - Expose mutation events that aren't just "some text content changed" > - Provide proper DOM traversal and manipulation APIs > - Generally be expressible in ways that aren't just inline JSON blobs > > It's bad enough that we are still awash in `<script > type="application/ld+json">` as barnacle on HTML semantics, but we > shouldn't keep adding to the damage. > There's an interesting question here, about what design patterns new kinds of structured metadata should follow, but the TAG's not likely to remember to answer that question if the only record is a comment in a Blink I2S. Can you propose a design principle <https://github.com/w3ctag/design-principles/issues>, if you think there is one here? Note that we're likely to listen to domain experts like Domenic, but we also have been uncomfortable in the past <https://github.com/w3ctag/design-reviews/issues/1000#issuecomment-2433471327> with using `<script type=...>` to wrap data that could have been embedded in another element that matched its semantics better. Jeffrey -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANh-dXnnYp_JCu%2B1yJgNzf8Jw3YWETMh3eGwEsBVEFQa%3DDZvqg%40mail.gmail.com.
