#24871: Textarea widget has redundant \r\n when writing XHTML
----------------------------------+------------------------------------
     Reporter:  tompecina         |                    Owner:  nobody
         Type:  Bug               |                   Status:  new
    Component:  Forms             |                  Version:  1.8
     Severity:  Normal            |               Resolution:
     Keywords:  textarea, widget  |             Triage Stage:  Accepted
    Has patch:  0                 |      Needs documentation:  0
  Needs tests:  0                 |  Patch needs improvement:  0
Easy pickings:  0                 |                    UI/UX:  0
----------------------------------+------------------------------------

Comment (by carljm):

 Yes, good point - I can see that in this case there's no elegant way for a
 subclass to change this behavior.

 A more general solution would be to move the HTML template into a class
 attribute that a subclass could override (or one of these days finally fix
 #15667).

 On further thought, I think I'm more inclined towards the class attribute
 than the parameter. The goal is to eventually move towards #15667, and
 once we arrive in that world (where all widget markup is overrideable via
 the template system) the existence of such a specific parameter for
 changing one aspect of rendering a `Textarea` would seem a bit of a wart,
 I think. Whereas moving the HTML template of a widget to a class attribute
 is consistent with other existing widgets, and offers a flexibility that's
 more similar to that of template-based widget rendering.

 Is anyone opposed to moving the HTML template for `Textarea` to a class
 attribute of the widget?

--
Ticket URL: <https://code.djangoproject.com/ticket/24871#comment:11>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.9f3cfe3bce817b3efb090843d7b3b8fd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to