It does, but it also doesn't. There are many times that you have a form that surrounds most of a page. While you have form components inside of that form that should obviously be disabled - because they are of no use, other components (such as links) may still be applicable / of use.
Tough to say - I could see it going either way. It's just that forms surround so much of many pages. -- Jeremy Thomerson http://www.wickettraining.com On Fri, Apr 17, 2009 at 1:21 PM, Igor Vaynberg <[email protected]>wrote: > this is so we are consistent with how we are handling security. if a > component is disabled then all of its children are also disabled, why > does that not make sense? > > -igor > > On Fri, Apr 17, 2009 at 8:37 AM, Jeremy Thomerson > <[email protected]> wrote: > > I just upgraded an app from 1.4-M2 to RC2 and found a weird behavior. I > > have a form that I enable / disable via a link on the page. Within that > > form, I have a table. Each row of the table is a DB object. In one > column, > > I have links to go to detailed view or edit pages. In the other columns, > I > > have labels if you're not in edit mode and textfields if you are in edit > > mode. > > > > Previously, the links were enabled regardless of the form's enabled > state. > > In RC2, if the form is disabled, the links are disabled. Why was this > > change made? Should it be that way (my feeling is no). > > > > -- > > Jeremy Thomerson > > http://www.wickettraining.com > > >
