Openbravo Issue Tracking System - POS2
View Issue Details
0047935POS2POSpublic2021-10-26 13:372023-07-26 13:51
normalminorhave not tried
0047935: Clicking on a default modifier doesn't go directly to the next step
When applying modifiers to a product with modifiers, if it has an option already selected(radio button) and you click it, it should switch to the next step with that property selected, but it doesnt.

A video explaining this is provided here: [^]
1. Open WebPOS with restaurant sampledata( [^])
2. Change to Restaurant Schema
3. Add a Cheeseburger
4. Try to click on Now(already selected, check screenshot) for cooking time.

Nothing happens, it should have switched to the next step. [^]
No tags attached.
png modifiersIssueSelect.png (57,522) 2021-10-26 13:37
Issue History
2021-10-26 13:37cbernerNew Issue
2021-10-26 13:37cbernerAssigned To => Retail
2021-10-26 13:37cbernerFile Added: modifiersIssueSelect.png
2021-10-26 13:37cbernerTriggers an Emergency Pack => No
2021-11-05 00:11guilleaerStatusnew => acknowledged
2021-11-09 14:42guilleaerProposed Solution updated
2021-11-09 15:27cbernerNote Added: 0132921
2021-11-10 01:59GremigerAssigned ToRetail => Gremiger
2021-11-10 02:00GremigerStatusacknowledged => scheduled
2021-12-24 05:19GremigerAssigned ToGremiger => Retail
2021-12-24 05:19GremigerStatusscheduled => acknowledged
2021-12-28 03:38hgbotNote Added: 0133997
2021-12-28 16:16cbernerAssigned ToRetail => Gremiger
2021-12-28 16:16cbernerStatusacknowledged => scheduled
2021-12-28 18:27cbernerReview Assigned To => cberner
2023-07-26 13:51guilleaerAssigned ToGremiger =>

2021-11-09 15:27   
Some more info to help out with the implementation of a solution:
David Baz prepared this JSFiddle with a mouseDown event which allows intercepting when the same radio button has been already pressed: [^]

It should also be tested using touch device(this may be setup from developer tools in chrome). In these cases it may be required to use touchEnd or touchStart events instead of the mouseDown(check if this last one is thrown, if so, use it, if not, find the one for touch device required to have the same behaviour).

Notice that the only event that knows the element has already been selected is the mouseDown one, which should generate an onChange one, so we know we have to switch to the next step. As the onChange is not automatically generated when clicking on an already selected radio button.
2021-12-28 03:38   
Merge Request created: [^]