Description of problem: Each time a cumin page attempts an update, if there were no updates to be made, the browser's console will display "Element main.tasks not found". Version-Release number of selected component (if applicable): mrg 2.0 How reproducible: 100% Steps to Reproduce: 1. Log in to cumin 2. Go to Grid/Schedulers (could be any page, but this is the case I was using) 3. Open the "console" of the browser and wait for the page to update Actual results: "Element main.tasks not found" shows-up in the console Expected results: There should not be any sort of debugging information that shows-up in the console. Additional info:
Fixed in revision 4861
Another unnecessary text which shows upon opening any Cumin page: Error: mismatched tag. Expected: </div>. Source File: Line: 1, Column: 91 Source Code: <html xmlns="http://www.w3.org/1999/xhtml"><div xmlns="http://www.w3.org/1999/xhtml">foo</foo></
I'm not seeing the text from comment #2. Which browser are you using? Do you have any other pages/tags open at the time (text from all open tabs will show-up in the same console window)?
firefox-3.6.18-1.el5_6 but also on Firefox 5.0 with the same error message from comment #2 in both. I am sure it is related to Cumin (tested with one tab only). Valid still on cumin-0.1.4887-1.el5
Though it is not a JavaScript error of course.
Is there a machine somewhere that I can vnc into so that I can see this happen? It doesn't seem to happen on any of my machines.
I am fine with postponing this bug, though the original problem was already resolved.
The above described problem can be easily reproduced with the latest build of Cumin (cumin-0.1.4916-1.el5) and any abovementioned Firefox (6.0 tested as well). The only possible source of "</foo>" string is mootools: $ cd mgmt-svn-newdata $ grep -r "</foo>" * 2>/dev/null | cut -d: -f1 cumin/instance/resources-wooly/mootools.js cumin/instance/resources-wooly/mootools.js wooly/instance/resources/mootools.js wooly/instance/resources/mootools.js wooly/resources/mootools.js wooly/resources/mootools.js
I was finally able to see this bug. Somehow, it looks like one of my plugins that I use for firefox must be hiding this error from me. When I used my windows machine and a clean copy of firefox, I was able to see the problem. It looks like this is indeed a bug in version 1.3.2 of the mootools library, which is the version that we are using. From what I can tell, it does not appear to be fixed in the latest (1.4.0) version of mootools. I will take a look at fixing this problem in the library. If it can be done without jeopardizing the overall integrity of the library, I will put the fix in, otherwise, I move to defer this BZ. Given that it doesn't affect the performance or functionality of cumin, I would consider this a very low priority item.
This is still a known issue in the mootools library. Given that it is not limiting any cumin functionality, I move that we set this to "WONTFIX". Presumably, it would get fixed naturally in a later version of mootools and we would pick it up sometime in the future.
In this case please prefer moving to another milestone instead of close it. Because closing it means forgive it but I think it's better to test it in next(3.0?) version.
Ok, that seems reasonable to me. I have updated the milestone. This BZ will serve as a reminder for me to check the status of the potential fix in the mootools library and fold it into cumin.
MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.