Details
-
Sub-task
-
Resolution: Done
-
Major
-
xCM 6.0.0
-
None
Description
I do not know the alogirthm used in order to make the category auto-completion form work but this is awfully long on IE6 (it even suddently directly close my engine without asking and I lost all the content of my title+big text). The CPU of your IE is at 100% for quite a long period of time.
It looks like behaving a bit better under FF3 (but still quite slow and CPU consuming for your PC)
[ If I remember correctly, Jahia 5 was implementing auto-completion only from 3+ char. Perhaps this could help]
TestRail: Results
Attachments
Activity
As decided by Elie and regarding the time we have before code freezing , please remove the filter field on category picker UI please. a new jira created for that purpose (JAHIA-4725 ) to be treated as user story during our next sprint
As discussed, regarding the remaining time we have before the code freeze up , an eventual solution would be disabling this auto-completion algorithm and make this filter working as an standard search as this is the case in Page picker , for this purpose you'll also need to add another panel for displaying the search result .
Please do a global estimation of the time needed for such a task before starting to work on that.
thx
Stephane Croisier (Inactive)
added a comment - Same is true on FF3 in fact.
Furthemore this is not clear at all how to test and if you should use wildcards or not.
First of all the alorithm is so slow that it is even difficult to enter your searched term carefully. A button to launch the search would then be more adequate. At least the editor could complete the searched term before the browsers explodes at 100% CPU.
Then (cf attachment on parent) I was looking after termes such as "Général" which are part of "Etat civil - Généralités" for instance. I do not know if this is due to accent or because I was not using any wildcards but this finds nothing (or I had to stop the script or kill my browser first).
Finally if I remember correctly, in Jahia 5, the auto-completion was sgessting some categories in a drop down.
Here this is a mix between a standard search (but which is executed dynamically each time you type a char) and an auto-completion suggestion list (drop-down).
Stephane Croisier (Inactive)
added a comment - Same is true on FF3 in fact.
Furthemore this is not clear at all how to test and if you should use wildcards or not.
First of all the alorithm is so slow that it is even difficult to enter your searched term carefully. A button to launch the search would then be more adequate. At least the editor could complete the searched term before the browsers explodes at 100% CPU.
Then (cf attachment on parent) I was looking after termes such as "Général" which are part of "Etat civil - Généralités" for instance. I do not know if this is due to accent or because I was not using any wildcards but this finds nothing (or I had to stop the script or kill my browser first).
Finally if I remember correctly, in Jahia 5, the auto-completion was sgessting some categories in a drop down.
Here this is a mix between a standard search (but which is executed dynamically each time you type a char) and an auto-completion suggestion list (drop-down). 
tested by the build 26953