Context Navigation

Changes between Initial Version and Version 1 of Ticket #24871, comment 9

initial	v1
3	3	Creating a custom widget subclass is not onerous. I do it all the time, for all sorts of reasons. My inclination is that that's an adequate solution for this case.
4	4
5		That said, I wouldn't have any problem with a `prepend_newline` parameter to `Textarea` which defaults to `True`. The justification for this is not so much XHTML5 specifically, and more just that the automatic new line stripping is conceptually odd behavior to begin with, added by browsers to workaround careless markup, and it seems reasonable to have a way to avoid that workaround and revert to what would otherwise be the straightforward intuitive behavior for the `Textarea` widget (that is, leaving the provided contents alone).
	5	That said, I wouldn't have any problem with a `prepend_newline` parameter to `Textarea` which defaults to `True`. The justification for this is not so much XHTML5 specifically, and more just that the automatic new line stripping is conceptually odd behavior to begin with, added by browsers to workaround careless markup, and it seems reasonable to have a way to avoid our workaround for that workaround and revert to what would otherwise be the straightforward intuitive behavior for the `Textarea` widget (that is, leaving the provided contents alone).
6	6
7	7	I do think the added new line behavior is something that ought to be documented regardless. Accepting this ticket on the basis that at least docs should be added.