User641687622 posted
Been tearing my hair out over one of those 'simple problems'!
I have written a fairly complex application that renders a menu of links, followed by a textbox where you can type in something to search for.
On an xHTML capable device everything is fine, same with stuff where it renders in HTML. But on some WML 1.1 devices, the links don't go anywhere, as the input (what the textbox renders as) expects something in it before it will allow you to leave the deck.
Oddly enough on some devices ASP .NET generates a new deck to put the control in, to get around this, but not on all devices.
I dug around and found that there's an attribute of '
input' inWML called '
emptyok'. By default it's false, hence my problem.
So I set out to add this to my textbox. With a regular asp:textbox you could just do
myTextBox.Attributes.add("emptyok", "true")
But you can't do this with mobile controls.
For the moment my work around is to design the form with a different deck for the input, but this is a bit of hack, unless you add
Next I tried a user control, with a regular asp:textinput and some device filters which figured out if they could add WML only attributes. The only problem was that getting the actual value back from an input control in WML is not like a normal page and I got
bogged down in writting my own <do> and <go> and <postfield> stuff, which I have given up for the moment.
So, any other ideas? Is there some clever way to overide rendering in the WML version and sneak emptyOK in there as well? This is quite fustrating, as having emptyok in mobile:textbox would have solved this one. Still, despite this MMIT is better than dealing
directly with WML.
Dylan
