-
-
Notifications
You must be signed in to change notification settings - Fork 436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove scriptaculous/effects.js dependency in js/prototype/validation.js #2609
Conversation
remove scriptaculous/effects.js dependency
good idea! what about we try to implement the fade effect in css only and we remove to call to Effect.fade completely? |
what about to implement fade effect with WAAPI seems its widly compatibly i have a ready solution:
|
Nice :) Tested. But we cannot remove effects.js now ... in admin config youll see this |
Why closed? |
sorry I accidentally closed this PR @sreichel yes its purpose is only giving a replacement for Effect.fade*() in a custom theme on frontend that not include scriptaculous/effects.js to optimize js size and the page load |
What do you think about removing fallback to effects.js? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm approving this since we can't remove scriptaculous at the moment, also the showAdvice() has a double implementation, using effects or not, so i guess it's correct to have the same for hideAdvice()
… js/prototype/validation.js (#2609)
cherry-picked to v20 since no conflicts |
Description (*)
if scriptaculous/effects.js is not loaded hideAdvice function return an error
make validation.js indipendent from scriptaculous/effects.js so we can remove this library to optimize page load
PS: like in showAdvice() function
Manual testing scenarios (*)
error advice not disappear and return error:
Uncaught ReferenceError: Effect is not defined