There is no consistent philosophy that lets us change tag attributes but not 
tag names once it's valid HTML.

These templates were not made for custom elements because they didn't exist, 
but it turns out supporting the custom element W3C standard is super easy: just 
let users set the tag name like you already let them set the tag attributes.

My point is that if Django used variables for tag names in its widget 
templates, it would suggest developers can build HTML that's consistent with 
W3C standards, which any web framework should support OOTB, and if that's not 
their philosophy then either W3C standards have to change either the web 
framework has to change.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/bUHwZWZ3hpfO4t7UOkIPHrzJpvyE72r63rm1ycGH9schtoIyl8lozWjHPCXt54Uz04AfccQxr2Pmjl5ZIAUR9oK-m-Z9Cci5Tdr0YFX_KEw%3D%40protonmail.com.
  • ... Adam Johnson
    • ... '1337 Shadow Hacker' via Django developers (Contributions to Django itself)
      • ... Carlton Gibson
        • ... '1337 Shadow Hacker' via Django developers (Contributions to Django itself)
          • ... Carlton Gibson
          • ... Tim Graham
          • ... '1337 Shadow Hacker' via Django developers (Contributions to Django itself)
          • ... Tim Graham
          • ... '1337 Shadow Hacker' via Django developers (Contributions to Django itself)
          • ... Tim Graham
          • ... '1337 Shadow Hacker' via Django developers (Contributions to Django itself)
          • ... '1337 Shadow Hacker' via Django developers (Contributions to Django itself)

Reply via email to