User tests: Successful: Unsuccessful:
Lately Joomla made some shift from mootools to jquery, for a number of scripts, thanks to the work of people participated on Joomla! Google Summer of Code Program in 2013. Although we use, let’s say, form validation in conjunction with jquery we still do call mootools as well. Which is wrong, as we increase the http requests without any benefits! So this PR tries to bring some sanity to what framework is loaded, by:
1 Removing uneeded calls for mt in cms/html/behavior.php
2 Corrects the multiselect.js script (and the uncompressed) to remove an error (Joomla is undefined)
3 Correct the view of administrator/com_users/views/mail/tmpl/default.php (chosen is called but not core.js)
4 Move all the calls from toolbar buttons to their respective layouts
Introduce jquery formvalidator for com_xxxxx
BUT ALSO CHECK THESE:
administrator/index.php?option=com_checkin should demonstrate multiselect without mt
administrator/index.php?option=com_users&view=mail should demonstrate form sent and validate without mt
administrator/index.php?option=com_modules should demonstrate multiselect and combobox without mt
http://localhost/administrator/index.php?option=com_admin&view=sysinfo should demonstrate highlighter.js without mt
Logout and log in to demonstrate the use of noframes without mt.
Labels |
Added:
?
|
Category | ⇒ | JavaScript |
Title |
|
@test success
-administrator/index.php?option=com_users&view=mail should demonstrate multiselect without mt
OK
administrator/index.php?option=com_modules should demonstrate multiselect and combobox without mt
OK
administrator/index.php?option=com_admin&view=sysinfo should demonstrate highlighter.js without mt
OK ... but sysinfo does not load highlighter.js. Tested with com_finder in front-end site, searching for a keyword and disabling everything but "Highlight Search Terms"
Login - Logout without mt
OK
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4888.
Some heads up informations:
These PRs have already two passing tests:
#5039 joomla/joomla-cms Introduce jquery formvalidator for com_admin
#5041 joomla/joomla-cms Introduce jquery formvalidator for com_banners
#5042 joomla/joomla-cms Introduce jquery formvalidator for com_config
#5043 joomla/joomla-cms Introduce jquery formvalidator for com_contact
#5044 joomla/joomla-cms Introduce jquery formvalidator for com_content
#5045 joomla/joomla-cms Introduce jquery formvalidator for com_finder
#5046 joomla/joomla-cms Introduce jquery formvalidator for com_languages
#5047 joomla/joomla-cms Introduce jquery formvalidator for com_menus
#5048 joomla/joomla-cms Introduce jquery formvalidator for com_messages
#5049 joomla/joomla-cms Introduce jquery formvalidator for com_modules
#5050 joomla/joomla-cms Introduce jquery formvalidator for com_newsfeed
#5051 joomla/joomla-cms Introduce jquery formvalidator for com_plugins
#5052 joomla/joomla-cms Introduce jquery formvalidator for com_redirect
#5053 joomla/joomla-cms Introduce jquery formvalidator for com_tags
#5054 joomla/joomla-cms Introduce jquery formvalidator for com_templates
#5056 joomla/joomla-cms Introduce jquery formvalidator for com_config ::frontend
#5058 joomla/joomla-cms Introduce jquery formvalidator for com_users
# 18 joomla-extensions/weblinks Introduce jquery formvalidator for com_weblinks
These need tests:
#5128 Smart search suggestion script from mootools to jquery
#5112 joomla/joomla-cms Introduce jquery formvalidator for com_contact ::frontend
#5113 joomla/joomla-cms Introduce jquery formvalidator for com_content ::frontend
#5114 joomla/joomla-cms Introduce jquery formvalidator for com_mailto ::frontend
#5115 joomla/joomla-cms Introduce jquery formvalidator for com_newsfeed ::frontend
#5116 joomla/joomla-cms Introduce jquery formvalidator for com_tags ::frontend
#5117 joomla/joomla-cms Introduce jquery formvalidator for com_wrapper ::frontend
And this one needs only review for typos:
#4895 joomla/joomla-cms Convert mootools document.id() to agnostic document.getElementId()
Question for PLT @Bakual, @infograf768 @chrisdavenport :
Any considerations for 3.4 inclusion?
@dgt41 Dimitris, link #18 above is broken: it should have been joomla-extensions/weblinks#18
Status | Pending | ⇒ | Ready to Commit |
We have 3 successful tests, moving to RTC.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4888.
Line 9 is blank in that file either in my version or the original. I am not a git expert, but is there some caching you can flush?
Do I need to rebase this?
Simply pull in the changes. You don't need to rebase.
I done something pretty stupid when I created this, instead of the proper origin: joomla-cms/staging I used my forked one. If I do anything this will be ruined big time! But now I figure it out how to use tower
Seriously now, sorry for this awkward situation
Labels |
Added:
?
|
When there is a will there’s a way
using gitshell I think it is:
git checkout yourbranch
git fetch upstream/pull/nnnn
git merge
I don't know with your GUI, but with the GUI provided by GitHub there are things you can't do and must use git commands (in gitshell, which is provided together with the GUI)
Status | Ready to Commit | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2014-11-20 09:58:42 |
@roland-d Any guidance for the documentation update? What we have is already outdated as from 3.3 we use jquery validation code
If this gets merged the documentation here needs also to be updated. Actually this is already outdated as the validate.js is jquery dependent since 3.3