Bug 7810 - The Toaster directory structure does not expand / collapse
Summary: The Toaster directory structure does not expand / collapse
Status: VERIFIED FIXED
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: 1.8
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 1.9 M3
Assignee: David Reyna
QA Contact: Cristina Agurida
URL:
Whiteboard:
: 8116 (view as bug list)
Depends on: 8558
Blocks:
  Show dependency tree
 
Reported: 2015-05-27 11:00 UTC by Belen Barros Pena
Modified: 2015-11-03 11:56 UTC (History)
8 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Belen Barros Pena 2015-05-27 11:00:12 UTC
The directories listed in the Toaster directory structure page (/dirinfo) should expand / collapse to show their contents. They are no longer doing so.

Found on master:a05663bfa10352fd5af6ca9a9d7b323c1c099f35
Comment 1 Belen Barros Pena 2015-08-06 13:46:50 UTC
*** Bug 8116 has been marked as a duplicate of this bug. ***
Comment 2 David Reyna 2015-08-19 07:34:12 UTC
The problem was that the original AJAX call in "dirinfo.html" expects the response data to be a JSON-formatted string, and uses "parseJSON()" to convert that into a JS object for display computation.

However, in debugging the code I found that the JS debugger recognized the "response" to now _already_ be a proper JS object, and the observed failure in the defect is that "parseJSON()" tries to convert it and immediately hits a syntax error. 

The fix is to simply skip the "parseJSON()" step, and now it all works. But I do not know why the AJAX operation changed, unless it was updated to take the JSON format indicator and perform the conversion automatically now, which would explain why it works the way it does in this release.

In any case, I have kept a note in the the patch indicated how "parseJSON()" is no longer needed, in case someone in the future puzzles over this.
Comment 4 Cristina Agurida 2015-10-22 14:42:12 UTC
This  issue can't be verified because the bug with 8558 id blocks it.
Comment 5 Cristina Agurida 2015-11-03 11:56:53 UTC
Verified on master: e1aa897beb33171bc902207b98c8f666b9e97ad3