Details
-
Type: Task
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.0.1
-
Fix Version/s: 3.1.0.BETA1, 3.1
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ICEfaces 3.0 ACE Components
-
Assignee Priority:P2
-
Affects:Compatibility/Configuration
Description
Original description for this issue:
"Currently the ACE Components leverage the mandatoryResource scheme to ensure that all required JavaScript resources are pre-loaded into the HEAD region of the page when the page is initially loaded (since head contents cannot be dynamically loaded later).
However, it would be advantageous if component JavaScript could instead be loaded dynamically at render time for the component in the body section of the page, similar to how the MOBI components work.
This task is to complete a survey of each ACE component to determine if their JavaScript resource are required to be loaded in the head region, or if the component can functional successfully if their JavaScript is loaded dynamically in the body region. Once we understand the scope of the head-region loading requirement we can better determine if it is feasible to permanently modify the components to load their JS dynamically in the body, etc."
To complete this, each component should be modified to use the dynamic body loading technique (instead of pre-loading in the head) and tested to determine if they continue to work, etc.
QA has extensive tests for each component that could be leveraged for this also."
Current description:
Find a way to update the 'head' element so that new JS or CSS resources are added dynamically to the page.
"Currently the ACE Components leverage the mandatoryResource scheme to ensure that all required JavaScript resources are pre-loaded into the HEAD region of the page when the page is initially loaded (since head contents cannot be dynamically loaded later).
However, it would be advantageous if component JavaScript could instead be loaded dynamically at render time for the component in the body section of the page, similar to how the MOBI components work.
This task is to complete a survey of each ACE component to determine if their JavaScript resource are required to be loaded in the head region, or if the component can functional successfully if their JavaScript is loaded dynamically in the body region. Once we understand the scope of the head-region loading requirement we can better determine if it is feasible to permanently modify the components to load their JS dynamically in the body, etc."
To complete this, each component should be modified to use the dynamic body loading technique (instead of pre-loading in the head) and tested to determine if they continue to work, etc.
QA has extensive tests for each component that could be leveraged for this also."
Current description:
Find a way to update the 'head' element so that new JS or CSS resources are added dynamically to the page.
Issue Links
- blocks
-
ICE-8125 Make head updating behaviour configurable
- Closed
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Ken Fyten
created issue -
Ken Fyten
made changes -
Field | Original Value | New Value |
---|---|---|
Salesforce Case | [] | |
Fix Version/s | 3.1 [ 10312 ] | |
Affects | [Compatibility/Configuration] | |
Assignee Priority | P2 | |
Assignee | Mircea Toma [ mircea.toma ] |
Mircea Toma
made changes -
Summary | Survey the ACE Components to verify the necessity of loading component JavaScript in head region vs. dynamically in body section | Implement head region update |
Salesforce Case | [] |
Mircea Toma
made changes -
Salesforce Case | [] | |
Description |
Currently the ACE Components leverage the mandatoryResource scheme to ensure that all required JavaScript resources are pre-loaded into the HEAD region of the page when the page is initially loaded (since head contents cannot be dynamically loaded later). However, it would be advantageous if component JavaScript could instead be loaded dynamically at render time for the component in the body section of the page, similar to how the MOBI components work. This task is to complete a survey of each ACE component to determine if their JavaScript resource are required to be loaded in the head region, or if the component can functional successfully if their JavaScript is loaded dynamically in the body region. Once we understand the scope of the head-region loading requirement we can better determine if it is feasible to permanently modify the components to load their JS dynamically in the body, etc. To complete this, each component should be modified to use the dynamic body loading technique (instead of pre-loading in the head) and tested to determine if they continue to work, etc. QA has extensive tests for each component that could be leveraged for this also. |
Original description for this issue: "Currently the ACE Components leverage the mandatoryResource scheme to ensure that all required JavaScript resources are pre-loaded into the HEAD region of the page when the page is initially loaded (since head contents cannot be dynamically loaded later). However, it would be advantageous if component JavaScript could instead be loaded dynamically at render time for the component in the body section of the page, similar to how the MOBI components work. This task is to complete a survey of each ACE component to determine if their JavaScript resource are required to be loaded in the head region, or if the component can functional successfully if their JavaScript is loaded dynamically in the body region. Once we understand the scope of the head-region loading requirement we can better determine if it is feasible to permanently modify the components to load their JS dynamically in the body, etc." To complete this, each component should be modified to use the dynamic body loading technique (instead of pre-loading in the head) and tested to determine if they continue to work, etc. QA has extensive tests for each component that could be leveraged for this also." Current description: Find a way to update the 'head' element so that new JS or CSS resources are added dynamically to the page. |
Mircea Toma
made changes -
Status | Open [ 1 ] | Closed [ 6 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Resolution | Fixed [ 1 ] | |
Status | Closed [ 6 ] | Reopened [ 4 ] |
Ken Fyten
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Fix Version/s | 3.1.0.BETA1 [ 10335 ] | |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Security | Private [ 10001 ] |
Ken Fyten
made changes -
Comment | [ A comment with security level 'icesoft-internal-developers' was removed. ] |
Ken Fyten
made changes -
Comment | [ A comment with security level 'icesoft-internal-developers' was removed. ] |
Ken Fyten
made changes -
Comment | [ A comment with security level 'icesoft-internal-developers' was removed. ] |
Ken Fyten
made changes -
Comment | [ A comment with security level 'icesoft-internal-developers' was removed. ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |