Re: [WICG/webcomponents] case-sensitive access to HTML attributes (as they were written) would be useful for framework authors (Issue #1076)

> I worry about how tools will handle this. They can assume that attribute and tag names are case-insensitive and lowercase them all. It might be hard to say that they now need to preserve the case on _everything_. Should case-reserving only be added to `<template parseparts>` and hope that tools can be updated to treat just that specially?

This is still backwards compatible: all existing apps with any tools that may have lowercased everything before sending it to the browser will still work.

People using the new feature would have to fix their tool, or pick a different tool. But to me this seems fine. It gives people *an option* that they don't have to use.

So, even if some people would have to consider switching tools, at least other people could start using it. I've personally haven't encountered a tool in any of my projects that lowercased my HTML.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/1076#issuecomment-2409178157
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/1076/2409178157@github.com>