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

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[POS2] POScriticalalways2021-06-14 18:582021-07-09 11:05
ReporterdmiguelezView Statuspublic 
Assigned Toplatform 
PriorityurgentResolutionopenFixed in Version
StatusacknowledgedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0047128: Error when focusing on the first element of a Form if this element is a Combo

DescriptionWhen the first element of a Form is a Combo, an error is thrown when trying to focus on it.
Steps To ReproduceLog in the Backend and go to the CRM Connector Configuration window
  - Select the record with the name 'Sample CRM Integration - Proxy'
  - In the API Property Tab select the record with API Key 'xCountry'
  - Set the 'Detail Sequence Number' as 1

Log in the FrontEnd and click on the customer button
Click on New Customer
It fails with the error: TypeError: Cannot read property 'focus' of null
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
dmiguelez (developer)
2021-06-15 09:27

Not backport for TAP is required as of now
jarmendariz (developer)
2021-06-16 18:09

I think that this issue should be related to something in the BaseForm. There is the storybook "Platform/Form Inputs/ComboBox/Focus Using Ref" where we set the focus of the Select component programatically and works as expected.
cberner (developer)
2021-06-29 13:23
edited on: 2021-07-01 16:03

It seems to actually be an issue with material-ui Select inputRef focus function, sometimes it is not available when the component is created, and the focus function will not work in that case, resulting in the error here.

This is the issue where they fixed this: [^]

Problem is, it has been done in material-ui version 5, we're currently using 4.11.3. Not sure how we should proceed here, there seems to be a workaround using setTimeout, but after further testing it doesn't seem to work in our case.

cberner (developer)
2021-07-09 11:05

This issue requires waiting for material-ui update to version 5(which is currently in beta as of now), this will fix this issue.

It has been marked as design-defect and resolution time removed until further notice.

- Issue History
Date Modified Username Field Change
2021-06-14 18:58 dmiguelez New Issue
2021-06-14 18:58 dmiguelez Assigned To => Retail
2021-06-14 18:58 dmiguelez Triggers an Emergency Pack => No
2021-06-15 03:51 prakashmurugesan88 Assigned To Retail => prakashmurugesan88
2021-06-15 03:51 prakashmurugesan88 Status new => scheduled
2021-06-15 09:27 dmiguelez Resolution time => 1624917600
2021-06-15 09:27 dmiguelez Note Added: 0129503
2021-06-16 18:02 dmiguelez Assigned To prakashmurugesan88 => jarmendariz
2021-06-16 18:04 dmiguelez Assigned To jarmendariz => platform
2021-06-16 18:07 dmiguelez Status scheduled => acknowledged
2021-06-16 18:09 jarmendariz Note Added: 0129579
2021-06-28 13:08 cberner Assigned To platform => cberner
2021-06-28 13:08 cberner Status acknowledged => scheduled
2021-06-29 13:23 cberner Note Added: 0129939
2021-07-01 16:03 cberner Note Edited: 0129939 View Revisions
2021-07-09 11:05 cberner Note Added: 0130348
2021-07-09 11:05 cberner Assigned To cberner => platform
2021-07-09 11:05 cberner Status scheduled => acknowledged
2021-07-09 11:05 cberner Resolution time 1624917600 =>
2021-07-09 11:05 cberner Type defect => design defect

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker