[MAGNOLIA-1505] contentNodeIterator varStatus.index does not start from 0 Created: 03/May/07 Updated: 23/Jan/13 Resolved: 24/Oct/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.5 RC1 |
| Type: | Bug | Priority: | Major |
| Reporter: | zam6ak | Assignee: | Fabrizio Giustina |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
varStatus.index in contentNodeIterator should start from 0 and not from 1. |
| Comments |
| Comment by zam6ak [ 03/May/07 ] |
|
Also, varStatus.count is reporting wrong value. if contentNodeIterator was supposed to follow JSTL forEach tag specs then varStatus definatelly does not behave as in forEach. Table 2. Properties of the LoopTagStatus object Now, the million dollar question.....What does contentNodeIterator provides that JSTL's forEach couldn't ??? |
| Comment by Sean McMains [ 04/May/07 ] |
|
This also seems to be affecting varStatus.last, which reports "true" one iteration before it should. |
| Comment by Fabrizio Giustina [ 24/Oct/07 ] |
|
status, first and last now works as expected. Count is right only when not using start/step, we should probably fix it while looking at |