- From: Erik Bruchez <ebruchez@orbeon.com>
- Date: Thu, 03 May 2007 12:33:11 +0800
- To: public-forms@w3.org
Good point. I thought we already specified that non-relevant triggers cannot be activated, but I can't find anything about this. I know that our implementation doesn't allow non-relevant controls to dispatch any event. Do we have a use case in favor of allowing non-relevant controls to dispatch events? -Erik Mark Birbeck wrote: > > Hi John, > > I think that captures it. :) > > The other thing that came up, which I for one hadn't thought of > before, was a need to clarify the behaviour of xf:triggers when they > appear inside a non-relevant group, or are themselves non-relevant. We > know that non-relevant controls should not _receive_ events, but > should we say that they don't initiate them either? In other words, > clicking a xf:trigger should have no effect? > > To clarify the situation I'm thinking of, we've said (at least in > XForms 1.1) that non-relevant controls act as if they aren't there in > the UI, and therefore don't receive events. But it is possible that > some processor might choose to render the controls--perhaps in a > greyed out style--but still not give them any events. That processor > would still have implemented the specification correctly. This > therefore opens up the possibility that a user could click on a > 'disabled' trigger, which in turn means that we need to be explicit > about the fact that the control should not generate any events. > > Regards, > > Mark > > On 02/05/07, John Boyer <boyerj@ca.ibm.com> wrote: >> >> I think we were pretty close to a conclusion on the telecon about the >> interpretation of the readonly MIP for trigger. >> >> Whatever the decision, it seems worthwhile make note of it in the spec >> given >> that we had some work to do getting through the points ourselves. >> >> Let's see if we can get this wrapped up on the list during the week >> and/or >> get a clear statement of resolution that folks can vote on next week if >> necessary. >> >> Here is what I understood from the discussion: >> >> 1) Like all other events for MIPs, the xforms-readonly and >> xforms-readwrite >> events are received by a trigger bound to a node (when the processing >> model >> says those events are to be dispatched, of course). >> >> 2) The readonly MIP is a statement about the what can happen to the data >> node. Since a trigger does not directly manipulate the data node via >> its >> UI binding, there is no direct relationship between the data node being >> readonly and presentational properties of the trigger. Specifically, >> >> a) The ability to activate a trigger is not disabled if the trigger is >> bound >> to a readonly node >> b) The default countenance of the trigger is unaffected, i.e. it does not >> take on a disabled countenance >> >> Cheers, >> John M. Boyer, Ph.D. >> STSM: Lotus Forms Architect and Researcher >> Chair, W3C Forms Working Group >> Workplace, Portal and Collaboration Software >> IBM Victoria Software Lab >> E-Mail: boyerj@ca.ibm.com >> >> Blog: >> http://www.ibm.com/developerworks/blogs/page/JohnBoyer >> >> > > -- Orbeon Forms - Web Forms for the Enterprise Done the Right Way http://www.orbeon.com/
Received on Thursday, 3 May 2007 04:33:22 UTC