Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 4.0
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Any
-
Assignee Priority:P2
Description
In the past, browser feature detection in client-side component code has been left at the discretion of the component developers and limited to the individual requirements of the various components. As a result, browser feature detection code is duplicated in many parts of our components' client-side code. In addition, some of that code uses deprecated methods of browser detection.
This improvement is to design and implement a centralized browser-feature detection strategy that can be used by any component (ACE, MOBI), making use of more reliable and current methods of browser feature detection. Most likely, this code should go in core.js.
This improvement is to design and implement a centralized browser-feature detection strategy that can be used by any component (ACE, MOBI), making use of more reliable and current methods of browser feature detection. Most likely, this code should go in core.js.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Priority | Major [ 3 ] | Minor [ 4 ] |
| Description | In the past, browser detection in client-side component code has been left at the discretion of the component developers and limited to the individual requirements of the various components. As a result, browser detection code is duplicated in many parts of our components' client-side code. Some of that code uses deprecated methods of browser detection. This improvement is to design and implement a centralized browser detection strategy that can be used by any component, making use of more reliable and current methods of browser detection. Most likely, this code should go in core.js. |
In the past, browser feature detection in client-side component code has been left at the discretion of the component developers and limited to the individual requirements of the various components. As a result, browser feature detection code is duplicated in many parts of our components' client-side code. In addition, some of that code uses deprecated methods of browser detection.
This improvement is to design and implement a centralized browser-feature detection strategy that can be used by any component (ACE, MOBI), making use of more reliable and current methods of browser feature detection. Most likely, this code should go in core.js. |
| Affects Version/s | EE-3.3.0.GA_P02 [ 11371 ] |
| Summary | Implement centralized browser feature detection strategy | Implement centralized browser feature-detection strategy |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Fix Version/s | 4.2.BETA [ 13091 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
A likely candidate for this is to leverage the Modernizr JS library (https://modernizr.com/), which is a lightweight, well supported 3rd party JS library for browser feature detection.
It might still be beneficial to centralize the APIs for this so the component's themselves are not exposed directly to the Modernizr APIs, if feasible.