Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XEP-0050: Undefined state in § 3.4 #307

Open
Flowdalic opened this issue Dec 3, 2016 · 0 comments
Open

XEP-0050: Undefined state in § 3.4 #307

Flowdalic opened this issue Dec 3, 2016 · 0 comments

Comments

@Flowdalic
Copy link
Contributor

As reported by goffi on the standards Mailing List:

There is a little issue with XEP-0050: in section 3.4 bullet 3, it's is
said that when the 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 is not contained by the , 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant