Viewing Issue Advanced Details
[ Jump to Notes ]
[ Wiki ]
|
[ View Simple ]
[ Issue History ]
[ Print ]
|
ID |
Category |
Type |
Reproducibility |
Date Submitted |
Last Update |
0000151 |
[In-Portal CMS] Admin Interfaces |
feature request |
N/A |
2009-07-28 04:31 |
2010-01-12 11:03 |
|
Reporter |
alex |
View Status |
public |
Project Name |
In-Portal CMS |
Assigned To |
|
Developer |
|
Priority |
normal |
Resolution |
open |
Platform |
|
Status |
active |
|
OS |
|
|
OS Version |
|
ETA |
none |
Fixed in Version |
|
Product Version |
5.0.0 |
|
Target Version |
Icebox |
Product Build |
|
Time Estimate | No estimate | |
|
Summary |
0000151: Ability to control load order of javascript code |
Description |
Currently we have various javascript code for various purposes and it works. Problems start to arise, when new functionality is implemented and this new javascript code should be run in specific exactly before/after kernel's code and no kernel code should changed.
In particular when you need to hide part of form fields based on external criteria, but at the end of the page there is no intelligence about page load results ( $(document).ready is not a criteria here ).
I propose to do one of the following:
1. add javascript hooks to most popular (guess on past customizations/projects) to allow to execute user's code in place where hook is called.
2. somehow create stack of code that should be called and add ability for user to scan that stack and insert his code after/before place he/she desires.
Sound hard to implement, but we should think about mentioned above abilities anyway.
|
Steps To Reproduce |
|
Additional Information |
|
Tags |
No tags attached. |
|
Reference |
|
Change Log Message |
|
Estimate Points |
0 |
|
Attached Files |
|
|