YUI Library

Thanks for the info

Hello Vasili,

The bug you are looking for is at

http://yuilibrary.com/projects/yui2/ticket/2418519

With respect to the migration, we are not able to create accounts for all
source forge users on the new system, it is up to the individual user to
create their account on the new site.

The easiest way to find an issue is to navigate to the tab corresponding
to the project under which the issue was filed - for this bug, that would
be YUI 2.x. You can then add the source forge ID of the bug in the text
field adjacent to the "Search Project" button. In this case 2418519. Then
press Search Project. The result will contain the link to the bug in the
YUILibrary Database. When you navigate to that link, you will find that
the full source forge history of the issue has been migrated to
YUILibrary.com. Please let me know if you need any further assistance in
finding your tracker items on YUILibrary.com.

how to find this ticket in yuilibrary.com?

I cannot find the ticket on http://yuilibrary.com for some reason!
It is very hard to use that tracker (and usernames seems not been
migrated, the history is not preserved).

The YUI project has been migrated from Source Forge to YUILibrary.com.
This ticket has been moved to the tracker on YUILibrary.com that
corresponds to the project it was filed against (YUI2, YUI3, Compressor,
etc.). All tickets not yet closed on Source Forge have been transferred
with their current state intact. The Source Forge instance of all tickets
is being marked as closed to avoid confusion. You can track the
status/progress of this ticket at http://yuilibrary.com/ using the same
ticket ID as it held in Source Forge.

The YUI project has been migrated from Source Forge to YUILibrary.com.
This ticket has been moved to the tracker on YUILibrary.com that
corresponds to the project it was filed against (YUI2, YUI3, Compressor,
etc.). All tickets not yet closed on Source Forge have been transferred
with their current state intact. The Source Forge instance of all tickets
is being marked as closed to avoid confusion. You can track the
status/progress of this ticket at http://yuilibrary.com/ using the same
ticket ID as it held in Source Forge.

Thank you for the solution for JSON type of request!

However our current case/page is more dynamic - where exactly the same
solution does not work :(
I just attached 2 test cases: refresh_test1.html (your working solution
for the previous usage) and
our case (refresh_test2.html).
The difference seems to be only in the usage of DataSource, in it's type
(JSARRAY).

How to make our usage (refresh_test2.html) working?

Thanks and Regards
vasili

File Added: refresh_test2.html

File Added: refresh_test1.html

this issue has been reviewed by the component owner who has provided the
following feedback:

In the sample code:

Instead of...

testData=testData2

...do this

dataSource.liveData = testData2;

and instead of...

dataTable.initializeTable();

...do this

dataSource.sendRequest(null,{success:dataTable.onDataReturnInitializeTable,scope:dataTable});

anybody here?

Hi guys,

could you please just give a clue?
(our managers are in the process of deciding - whether to use YUI Table,
and this issue is somehow critical: without it - no instant update of cells
- when there are scrollbars and a lot of data).

thanks and regards

And also after
dataTable.initializeTable();
call - no cell editors! (pressing tab - we rebuild DataTable)

This bug report is being forwarded to the author or current owner of the
affected component for additional investigation and response.