[ECOMMERCE-260] Use updated JQuery version from Core Created: 16/Oct/19 Updated: 27/Jun/23 Resolved: 25/Oct/19 |
|
| Status: | Closed |
| Project: | E-commerce |
| Component/s: | None |
| Affects Version/s: | 1.0 |
| Fix Version/s: | 1.1 |
| Type: | Story | Priority: | Neutral |
| Reporter: | Ilgun Ilgun | Assignee: | Evzen Fochr |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 1.5h | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Date of First Response: | |||||
| Sprint: | Add-Ons 23 | ||||
| Story Points: | 0.5 | ||||
| Description |
|
Currently, we bring our own Jquery version and the library, ideally, we should simply use the version from usual Magnolia classpath. Core team currently updates Jquery because of some security vulnerabilities, we should follow the same pattern here.
AC
|
| Comments |
| Comment by Aleksandr Pchelintcev [ 16/Oct/19 ] |
|
> Use the library from the classpath Don't quite get what this means/how are you planning to do that. JQuery is a script just lying somewhere in resource directory in admincentral. It's not Java classpath. Another concern - why trying to use jquery that admincentral uses in some ftls? Ftls are there for page rendering, have different lifecycle than admincentral, have little to do with each other, don't they? My proposal would be to not use JQuery at all and learn the vanilla JS ways of searching for elements (they're quite advanced and stadartised these days). |