Difference between revisions of "XEP-Remarks/XEP-0050:Ad-Hoc Commands"

From XMPP WIKI
Jump to: navigation, search
(Created page with "== Undefined Sate == There is a little issue with XEP-0050: in section 3.4 bullet 3, it's is said that when the <actions/> element is present: - The action "execute" is al...")
 
Line 4: Line 4:
 
said that when the <actions/> element is present:
 
said that when the <actions/> element is present:
  
- The action "execute" is always allowed, and is equivalent to the  
+
* The action "execute" is always allowed, and is equivalent to the action "next".
action "next".
+
* The "next" action is typically the "next" button or option in a wizard. If <next/> is not contained by the <actions/>, it is disabled.
- The "next" action is typically the "next" button or option in a  
+
wizard. If <next/> is not contained by the <actions/>, it is disabled.
+
  
 
So if "next" action is disabled, execute is allowed but equivalent to a  
 
So if "next" action is disabled, execute is allowed but equivalent to a  

Revision as of 15:06, 21 February 2018

Undefined Sate

There is a little issue with XEP-0050: in section 3.4 bullet 3, it's is said that when the <actions/> element is present:

  • The action "execute" is always allowed, and is equivalent to the action "next".
  • The "next" action is typically the "next" button or option in a wizard. If <next/> is not contained by the <actions/>, it is disabled.

So if "next" action is disabled, execute is allowed but equivalent to a disabled action.

I have had an issue which seems related to this confusion with SleekXMPP and Gajim: if the next action is disabled in sleekXMPP, Gajim still show the "execute" button, but a click on it result in an error, while the "finish" button act as expected.

My guess is that "execute" should be equivalent to "complete" when "next" is not possible (but what if "complete" is disabled too ?).

Original standards@ post: https://mail.jabber.org/pipermail/standards/2015-August/030137.html