• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Bug in WOTextField?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug in WOTextField?


  • Subject: Re: Bug in WOTextField?
  • From: "Mr. Pierre Frisch" <email@hidden>
  • Date: Fri, 22 Feb 2008 08:37:03 -0800

I cannot concur more, I have fallen in that trap many time. May be we could make a request for HTML 5 :)

Pierre
--
Pierre Frisch
email@hidden


On Feb 22, 2008, at 5:29, Mike Schrag wrote:

Nevertheless I'm still wondering, why WOTextField happily sets the value to null on its binding, even though it's name doesn't appear in the formValueKeys...
This topic was discussed (most recently) in the thread "Partial Form Submit" from Jan 30 ... My personal conclusion about fixing it and why it is like that:

"I actually have avoided putting this in Wonder because I'm really not sure what the side-effects might be in the general case. I've always felt like the current behavior is wrong, but I feared changing it in case it introduced some subtle bugs somewhere, or in case people depended on that wacky behavior. I suspect the original WO folks made it work like this so that checkbox and the others would work in a consistent way. The real blame is on the original design of how unchecked checkboxes submit in HTML, but not much we can do about that :) It is a bit a conundrum, though ... If you change it, you always have to lug around the 'oh, btw, checkboxes don't work the same way' note."

In the case of Ajax, we can fix this (although I ended up fixing partial form submit in a different way) with the suggestions of including the list of submitted form keys along with the form. In the general submit case (i.e. non-Javascript submit), though, it's a lot more annoying and tricky to try and pull off that fix. So basically you either accept the current behavior in its consistently across all elements, or you fix it for everything except WOCheckBox, which could be really confusing. Honestly, I'm torn on this.

ms

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Bug in WOTextField? (From: Timo Hoepfner <email@hidden>)
 >Re: Bug in WOTextField? (From: Alexander Spohr <email@hidden>)
 >Re: Bug in WOTextField? (From: Timo Hoepfner <email@hidden>)
 >Re: Bug in WOTextField? (From: Mike Schrag <email@hidden>)

  • Prev by Date: Yet another bug in EODistributedClassDescription
  • Next by Date: Re: Rant: Why I hate Java Client
  • Previous by thread: Re: Bug in WOTextField?
  • Next by thread: Yet another bug in EODistributedClassDescription
  • Index(es):
    • Date
    • Thread