[JIRA] [core] (JENKINS-18119) table.sortable may be null in a ProgressiveRendering callback

[jgl...@cloudbees.com (JIRA)]

Jesse Glick created JENKINS-18119 table.sortable may be null in a ProgressiveRendering callback Issue Type: Bug Assignee: Unassigned Components: core Created: 28/May/13 4:39 PM Description: Turn Jenkins security on and create a single user and log in. Now start reloading /asynchPeople over and over. Sometimes it is fine; other times the progress bar is broken and the browser console shows an error: Uncaught TypeError: Cannot call method 'refresh' of undefined @localhost:78 display @localhost:78 checkNews @progressiveRendering.js:29 The TABLE.sortable rule defined the sortable property on a table, yet this might be after the first rendering callback, if that is quick enough. https://github.com/jenkinsci/jenkins/commit/8bcc07326d26ad4f2e9b826d2b05a67e97acd3e5#L0L183 seems to have caused this regression. Previously, it was guaranteed that ts_refresh was defined, and if ts_makeSortable had not been called, then no real harm was done. Now the sortable member might be null, so the code in the AsynchPeople view as of ac7e277—and the recommendation in ProgressiveRendering Javadoc—is unsafe. Project: Jenkins Labels: _javascript_ regression Priority: Major Reporter: Jesse Glick

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.