Back to Ideas
9
Like
Follow Idea
When moving a button do not change it to default
1019Views
5Comments
Implemented
Frontend (App Interfaces)
Platform Server Release Oct.2019 CP1

In a screen or web block that does not have a default button, moving a button will make that button default.

This behavior should not happen because if the button is 'not default' it should remain as 'not default' as the developer is only moving the button, not changing its behavior.

Video (20s) examplifying the idea : https://youtu.be/dbSaE_6w_wo

--Tiago Bernardo

23 Aug 2019
Copy link to comment
Changed the category to
Frontend
23 Aug 2019
Copy link to comment

I believe that this should be reported as a bug, I certainly consider it to be one.

J.Ja

24 Aug 2019
Copy link to comment
Changed the status to
Working on it
expected delivery in Q4 2019

Hi Tiago,

That's a good suggestion. In fact, as Justin was saying, that is a small bug.You'll be happy to know that we're working on the next generation of web applications , where that, along with  several other suggestions, will be released. (You'll even be able to have different forms on the screen, with different default buttons). We'll share more about this soon. 

Thanks,
Tiago Simões

09 Sep 2019
Copy link to comment
Changed the status to
Implemented
on 02 Oct 2018

Hi Tiago,

We've just released the new reactive web apps, where we made sure this annoying UX glitch would be fixed. Read more about all the improvements in Reactive Web Apps in this forum post. 

Thanks for your idea,
Tiago Simões

21 Oct 2019
Copy link to comment

Hi Tiago,

Thanks for the update.

Looking forward to embracing the new Reactive We Apps!

--Tiago Bernardo

22 Oct 2019
Copy link to comment