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


Ignore:
Timestamp:
Sep 1, 2026, 4:01:26 PM (43 hours ago)
Author:
Jacob Walls

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #30306, comment 9

    initial v1  
    44> For `Input` subclasses, `input_type` corresponds to `<input type="...">`. `ChoiceWidget` uses `input_type` for a different purpose.
    55
    6 When I look at `RadioSelectTest.test_render()` I see that the `RadioSelect.input_type` does flow through to an eventual `<input type="radio">`. I only see a couple tests for `ChoiceInput` itself, in a unit test style. `RadioSelect` is documented; `ChoiceWidget` isn't. Just sounding out why I think the request makes sense -- `Textarea` is a documented widget, and the request to make it quack like the others seems like it comes up in actual usage.
     6When I look at `RadioSelectTest.test_render()` I see that the `RadioSelect.input_type` does flow through to an eventual `<input type="radio">`. I only see a couple tests for `ChoiceWidget` itself, in a unit test style. `RadioSelect` is documented; `ChoiceWidget` isn't. Just sounding out why I think the request makes sense -- `Textarea` is a documented widget, and the request to make it quack like the others seems like it comes up in actual usage.
Back to Top