Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[POS2] POSminorhave not tried2021-10-26 13:372023-07-26 13:51
ReportercbernerView Statuspublic 
Assigned To 
PrioritynormalResolutionopenFixed in Version
StatusscheduledFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned Tocberner
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0047935: Clicking on a default modifier doesn't go directly to the next step

DescriptionWhen 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: [^]
Steps To Reproduce1. 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.
Proposed Solution [^]
TagsNo tags attached.
Attached Filespng file icon modifiersIssueSelect.png [^] (57,522 bytes) 2021-10-26 13:37

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
cberner (developer)
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.
hgbot (developer)
2021-12-28 03:38

Merge Request created: [^]

- Issue History
Date Modified Username Field Change
2021-10-26 13:37 cberner New Issue
2021-10-26 13:37 cberner Assigned To => Retail
2021-10-26 13:37 cberner File Added: modifiersIssueSelect.png
2021-10-26 13:37 cberner Triggers an Emergency Pack => No
2021-11-05 00:11 guilleaer Status new => acknowledged
2021-11-09 14:42 guilleaer Proposed Solution updated
2021-11-09 15:27 cberner Note Added: 0132921
2021-11-10 01:59 Gremiger Assigned To Retail => Gremiger
2021-11-10 02:00 Gremiger Status acknowledged => scheduled
2021-12-24 05:19 Gremiger Assigned To Gremiger => Retail
2021-12-24 05:19 Gremiger Status scheduled => acknowledged
2021-12-28 03:38 hgbot Note Added: 0133997
2021-12-28 16:16 cberner Assigned To Retail => Gremiger
2021-12-28 16:16 cberner Status acknowledged => scheduled
2021-12-28 18:27 cberner Review Assigned To => cberner
2023-07-26 13:51 guilleaer Assigned To Gremiger =>

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker