On Mon, Jun 23, 2008 at 10:01:43AM +0000, corvid wrote:
Jeremy wrote:
On Mon, Jun 23, 2008 at 05:05:29AM +0000, corvid wrote:
In SELECT, if standard_widget_colors is set, color and backgroundColor are set to NULL. ...
This is done for most input types in form.cc, not just SELECT, see: * Html_tag_open_input() * Html_tag_open_isindex() * Html_tag_open_select()
However it is not done in: * Html_tag_open_button() * Html_input_image()
The first three show fltk widgets.
Hmm, whereas the other two create a ComplexButtonResource that does not.
Is the potential crash only an issue for SELECT inputs? If so, why?
INPUT and ISINDEX don't have close tags, so other tags can't be sneaked inside them.
Thanks for that. This is the bit of form.cc that I understand least which is why I have all these questions. I want to refactor the various code paths that lead to AddInput() but every time I look I see more ways in which they do things differently. The paths that call Html_tag_open_button() and Html_input_image() are particularly tricky and refactoring them correctly depends on understanding the DilloHtml stack, widget styles and layouts etc. Regards, Jeremy Henty