Context Navigation

Changes between Version 1 and Version 2 of Ticket #38799, comment 2

v1	v2
9	9	1) to be able to simply populate the dependency description in an object that extends the api one.
10	10	2) to make sure dynamic section / settings/ controls are taken into account ( the api.Value::when() method and the api 'change' event are our friends for that ).
11		3) to make sure that cross section dependencies work fine, even in a lazy load context ( which will be implemented in the future as far as I understand). For that, this dependency class has to make sure that a control not yet instantiated has to be sort of "awaked".
	11	3) to make sure that cross section dependencies work fine, even in a lazy load context ( which will be implemented in the future as far as I understand). For that, this dependency class has to make sure that a control not yet instantiated has to be sort of "awaken".
12	12
13	13	Let me know if / how I can help further on this. I'll be happy to if I can.