Last modified: 2007-01-14 12:04:25 UTC
Not sure how to describe this. Sorry if I'm a bit roundabout. I tried out the new cascading protection on en.wikipedia.org, and everything seems to work well enough, except for one thing: usually, when I protect a page, the edit shows as on-top, but when I use cascading protection, it doesn't. In fact, an *older* edit still shows as on-top. Page history shows the correct order, but when looking at a specific diff, the newest version (when protecting/unprotecting) will still show a "next diff" link, which appears to compare against the most recent non-protection edit. Example from [[w:en:Special:Contributions/Luna Santin]]: # 03:41, January 14, 2007 (hist) (diff) m User:Luna Santin/sandbox (Unprotected User:Luna Santin/sandbox: Testing unprotection) # 03:40, January 14, 2007 (hist) (diff) User:Luna Santin/sandbox (wonder what happens to history if we edit while cascade-protected) (top) [rollback] # 03:39, January 14, 2007 (hist) (diff) m User:Luna Santin/sandbox (Protected User:Luna Santin/sandbox: Huh, is it borked? Edits not showing on-top [edit=autoconfirmed:move=autoconfirmed]) Notice that the wrong edit is labelled on-top. The full page history still shows the correct order, but when viewing diffs, this causes a few odd problems.
Does not appear to be limited to the use of cascading protection; I see this when making non-cascading protection.
Fixed in r19228.
