Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Should we have a "Next" button when performing the OAuth dance #282

Closed
syndesis-bot opened this issue Nov 15, 2017 · 2 comments
Closed

Should we have a "Next" button when performing the OAuth dance #282

syndesis-bot opened this issue Nov 15, 2017 · 2 comments
Assignees
@seanforyou23
Labels
cat/starter An issue which is easy to solve and can be used for ramping up new developers group/ui User interface SPA, talking to the REST backend notif/uxd Ping UX team that UX related changes are involved prio/p2 The priority of a bug. p1 means low

Comments

@syndesis-bot
Copy link
Collaborator

@zregvart 2017-11-06 good first issue, Priority - Low, UX Design

It doesn't do anything so we might as well remove it?

selection_306
@syndesis-bot syndesis-bot added cat/starter An issue which is easy to solve and can be used for ramping up new developers group/ui User interface SPA, talking to the REST backend notif/uxd Ping UX team that UX related changes are involved prio/p2 The priority of a bug. p1 means low labels Nov 15, 2017
@syndesis-bot
Copy link
Collaborator Author

@gashcrumb 2017-11-06

Agreed, that next button should go away when oauth is involved...

I wonder actually if the back/next buttons would be better placed down underneath the form when it's showing instead of up at the breadcrumb bar.

@syndesis-bot
Copy link
Collaborator Author

@deeleman 2017-11-07

I wonder actually if the back/next buttons would be better placed down underneath the form when it's showing instead of up at the breadcrumb bar.

+1 to that

And if so, the next button would override the "Connect ..." CTA, or just trigger the same action.

@syndesis-bot syndesis-bot mentioned this issue Nov 16, 2017
Closed
@seanforyou23 seanforyou23 self-assigned this Jan 9, 2018
@seanforyou23 seanforyou23 mentioned this issue Jan 9, 2018
Merged
paoloantinori pushed a commit that referenced this issue May 23, 2019
@pure-bot
Merge pull request #282 from gashcrumb/issue-279
d2a5257
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@seanforyou23 seanforyou23

Labels
cat/starter An issue which is easy to solve and can be used for ramping up new developers group/ui User interface SPA, talking to the REST backend notif/uxd Ping UX team that UX related changes are involved prio/p2 The priority of a bug. p1 means low
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@seanforyou23 @syndesis-bot