Timeline for 2 buttons that do the same thing
Current License: CC BY-SA 4.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 28, 2020 at 23:38 | vote | accept | Nate Gines | ||
| Feb 27, 2020 at 11:53 | comment | added | Mast | If the client explicitly asks for it, it's a good idea to deliver what he asks unless you get them sold on a better idea. "Allowing it" isn't applicable. | |
| Feb 27, 2020 at 10:14 | comment | added | Mathijs Segers | This is actually pretty common, you see it often on pages like you described. For people who know what they want, they can hit the button on the top of the page, if not read some description and maybe apply after reading (without the scrolling) | |
| Feb 27, 2020 at 9:02 | comment | added | Jonathan | A lot of paged-list navigation pages has their buttons (next/prev/etc) in the top and bottom of the list as well. | |
| Feb 27, 2020 at 8:54 | answer | added | knallfrosch | timeline score: 63 | |
| Feb 27, 2020 at 7:52 | comment | added | bracco23 | As an example of this, application for an indian visa have a multi-page form where each page has control buttons both at top and bottom. Useful in this case because pages tend to be long and not always you are interested in their full content (form might be already filled) so you can just use the top to go forward, or use the bottom one if you scrolled to see the content. | |
| Feb 27, 2020 at 3:00 | history | tweeted | twitter.com/StackUX/status/1232863097637023744 | ||
| Feb 27, 2020 at 1:22 | history | became hot network question | |||
| Feb 26, 2020 at 23:04 | comment | added | Michael Lai♦ | Is the client's view/opinion relevant? What would the users think? I think it depends on the particular use case and context but a screen shot or mockup would be helpful. | |
| Feb 26, 2020 at 21:55 | answer | added | It's Dylan | timeline score: 1 | |
| Feb 26, 2020 at 20:24 | comment | added | ph33nyx | I would say it's not the best practice if both are visible at the same time. Perhaps having one button in a fixed position (so that it does not scroll) is a better solution to having that option visible at all times. | |
| Feb 26, 2020 at 19:47 | answer | added | user_is_not_dumb | timeline score: 1 | |
| Feb 26, 2020 at 19:25 | comment | added | MetalMikester | I echo Paran0a's sentiment: It very much depends on the interface. I've seen this done correctly and also incorrectly. | |
| Feb 26, 2020 at 18:34 | comment | added | Paran0a | Extremely difficult to tell if we don't see how your user interface looks. It could be that its perfectly fine and sensible, but it could also be that its wrong. | |
| Feb 26, 2020 at 17:47 | answer | added | Chris Griffith | timeline score: 15 | |
| Feb 26, 2020 at 17:29 | history | edited | Sooraj MV | CC BY-SA 4.0 |
added relevant tags
|
| Feb 26, 2020 at 17:20 | review | First posts | |||
| Feb 27, 2020 at 4:42 | |||||
| Feb 26, 2020 at 17:15 | history | asked | Nate Gines | CC BY-SA 4.0 |