Thursday, 27 November 2008

Gripe #7: empty field values

Not a lot to say about this one, it's just so obviously wrong. An empty value isn't really an empty value, not according to RedDot. An empty value is treated in the same way as not specifying a value i.e. the default value overrides it.

This is just so incredibly annoying, and I cannot fathom quite how it can't be fixed. Surely it's a no-brainer? The workaround always involves doing stupid things like putting in an HTML comment for the value. Crazy.

3 comments:

Anonymous said...

It seems, you're not familiar with Rendertags.
If you want to have the "value without value", use ".value". If you want to have the value with the default value, use ".GetHtml()".
In the IT world, it is a must for a lifelong learning... and not complaining old issues...

Anonymous said...

It seems that the previous comment writer is not familiar with the difference of "value to be rendered" and "rendered value". Not everything that works for some examples is a suitable general solution.

Anonymous said...

Hope they didn't sent their hitman...
Jonathan, what's up with a reply to my mail?
Cheers, the RedDot jedi