On Thu, 4 Dec 2008, Markus Ernst wrote:
Ian Hickson schrieb:
Why is that a problem? Is converting one to the other a common occurance?
I'm not really convinced it's that much work. Assuming that the radio
buttons and/or checkboxes are written in a consistent manner, which
they
On Thu, 4 Dec 2008, Markus Ernst wrote:
This CSS3 module is indeed an interesting approach, anyway I don't see
in this spec how possible conflicts between the form structure and it's
presentation can be avoided or handled. Start with:
select name=gender
option value=fFemale/option
Ian Hickson schrieb:
[...]
Why is that a problem? Is converting one to the other a common occurance?
I'm not really convinced it's that much work. Assuming that the radio
buttons and/or checkboxes are written in a consistent manner, which they
usually are, a simple regexp search-and-replace
Eduard Pascual schrieb am 29.10.2008 18:37:
On Wed, Oct 29, 2008 at 9:49 AM, Markus Ernst [EMAIL PROTECTED] wrote:
Consider a form with some quite big radio button groups, and now you have do
add some more options. After you are done, your boss says: Ok, great
work... but this looks too ugly
On Thu, Dec 4, 2008 at 12:45 PM, Markus Ernst wrote:
Eduard Pascual schrieb am 29.10.2008 18:37:
On Wed, Oct 29, 2008 at 9:49 AM, Markus Ernst [EMAIL PROTECTED] wrote:
Consider a form with some quite big radio button groups, and now you have
do
add some more options. After you are done,
Ian Hickson schrieb:
On Tue, 28 Oct 2008, Markus Ernst wrote:
[...]
I consider a total re-thinking of select, input type=checkbox and
input type=radio elements as highly desirable, though I see that this
might cause more serious backwards compatiblity problems than for
example removing the
On Wed, Oct 29, 2008 at 9:49 AM, Markus Ernst [EMAIL PROTECTED] wrote:
Consider a form with some quite big radio button groups, and now you have do
add some more options. After you are done, your boss says: Ok, great
work... but this looks too ugly now, just change it into those dropdown kind
