Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0032425Openbravo ERPA. Platformpublic2016-03-07 13:192022-02-01 08:09
Reporteralostale 
Assigned ToTriage Platform Base 
PriorityurgentSeveritymajorReproducibilityhave not tried
StatusacknowledgedResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0032425: request on keystroke while typing on selector's drop down
DescriptionWhen using a selector drop down to select an item, a request to datasource is performed on each keystroke regardless the time elapsed between them is very small.

This causes an unneeded backend overload.

When filtering in grid (in standard windows or selector popup) there is a delay between keystroke and request, so that in case several keystrokes are done within this delay period, a single request is executed grouping all of them.

The problem is related with the implementation of fireOnPauseDelay in SC. Writting some characthers in a selector in less time than fetchDelay (200ms) time. This works properly. But if just in that moment, it will begin to type several times any key, lots of request are triggered.
Steps To Reproduce* Open Sales Order and create a header
* Create a line
* Focus on product drop down and start typing "as" several times
  -> Note lots of requests are triggered. fetchDelay (default 200ms) is not applied properly.
Proposed SolutionRefactor or improve fireOnPauseDelay to take into account this problem.
Additional Information
TagsPerformance
Relationships
related to design defect 0030312 acknowledged Triage Platform Base adaptive filtering is not working in selectors 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2016-03-07 13:19alostaleNew Issue
2016-03-07 13:19alostaleAssigned To => platform
2016-03-07 13:19alostaleModules => Core
2016-03-07 13:19alostaleTriggers an Emergency Pack => No
2016-03-07 13:19alostaleStatusnew => acknowledged
2016-03-07 13:19alostaleTag Attached: Performance
2016-03-07 13:21alostaleTarget Version => 3.0PR16Q2
2016-03-22 10:20alostaleTarget Version3.0PR16Q2 => 3.0PR16Q3
2016-05-18 17:43alostaleStatusacknowledged => scheduled
2016-05-18 17:43alostaleAssigned Toplatform => inigosanchez
2016-05-19 12:49inigosanchezSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=12167#r12167
2016-05-19 13:00inigosanchezSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=12168#r12168
2016-05-23 12:24alostaleRelationship addedrelated to 0030312
2016-05-24 13:03inigosanchezNote Added: 0086703
2016-05-24 15:18inigosanchezAssigned Toinigosanchez => platform
2016-05-24 15:18inigosanchezStatusscheduled => acknowledged
2016-05-24 15:18inigosanchezTypedefect => design defect
2016-05-24 15:18inigosanchezDescription Updatedbug_revision_view_page.php?rev_id=12223#r12223
2016-05-24 15:18inigosanchezProposed Solution updated
2016-06-27 11:49caristuTarget Version3.0PR16Q3 =>
2022-02-01 08:09alostaleAssigned Toplatform => Triage Platform Base

Notes
(0086703)
inigosanchez   
2016-05-24 13:03   
Updated proposed solution and promoting to design defect because it will require much more effort + testing.