Ticket #2532117 (accepted enhancement)
Reporter  Derek Gathright |
Opened: 04/6/12 Last modified: 03/15/13 Status: accepted Type: enhancement |
Owner Derek Gathright |
Target Release: BACKLOG Priority: P3 (normal) |
|---|---|---|---|
| Summary: | Improve Scrollview's ability to dynamically introduce new "pages" to paginated instances | ||
| Description: | It it currently possible, but a little hacky. A proper public API should be introduced to allow this to occur more easily Currently looks like: scrollView.pages._pageNodes.push(Y.Node.create('<li>1</li>')); Origin of new content would be from an XHR call, disk, etc... Also provide an documentation example. |
||
| Type: | enhancement | Observed in Version: | development master |
| Component: | ScrollView | Severity: | S3 (normal) |
| Assigned To: | Derek Gathright | Target Release: | BACKLOG |
| Location: | Library Code | Priority: | P3 (normal) |
| Tags: | Relates To: | ||
| Browsers: | N/A | ||
| URL: | |||
| Test Information: | |||
Change History
|
Posted: 04/6/12
|
|
Posted: 05/8/12
|
|
Posted: 05/8/12
|
|
Posted: 07/21/12
|
|
Posted: 08/1/12
Moving 3.7.0 bugs to 3.6.x for triage. |
|
Posted: 09/19/12
Moving from 3.6.x to 3.CURRENT.NEXT |
|
Posted: 09/24/12
|
|
Posted: 01/28/13
|
|
Posted: 01/28/13
|
|
Posted: 03/15/13
|
While no official API is in place yet, the work done for #2532118 improves paginated instances with dynamically added pages by calculating the target offset on the fly as opposed to relying on values calculated at instantiation. #2532289 will help out if we run into performance issues with that approach.