Index: test/minefield/minefield.html
===================================================================
--- test/minefield/minefield.html	(revision 757)
+++ test/minefield/minefield.html	(working copy)
@@ -1,6 +1,30 @@
 <html>
   <head></head>
   <body>
+<p>
+HOUSTON, Texas (AP) -- NASA managers cleared Discovery to return home Friday, planning for a possible touchdown in New Mexico for only the second time in space shuttle history because of bad weather on both coasts.
+
+As the crew woke up to Christmas music Friday morning, they still didn't know where the spacecraft would touch down.
+
+"I have a lot of things to worry about on this flight that I can control, and the weather is something I can't," Discovery commander Mark Polansky told reporters from space. "I'm ready to land at any of the three sites."
+
+Discovery needs to be on the ground Saturday or it could run out of the fuel that powers its electrical system.
+
+NASA normally has more time for the landing, but the astronauts spent an extra day at the international space station this week to work on a stubborn solar array.
+
+Rain and clouds were forecast during the shuttle's first landing opportunity Friday afternoon at Kennedy Space Center in Florida, and crosswinds were expected at NASA's next-best option, Edwards Air Force Base in California's Mojave Desert.
+
+The third option, White Sands Space Harbor in New Mexico, hasn't been used for a shuttle landing in 24 years, and in that landing, sand on the runway contaminated the orbiter, and the brakes were damaged. It isn't normally equipped to service the shuttles, either.
+
+NASA managers hoped the weather would clear at one of the favored sites by the first landing opportunity, but they shipped a crane to White Sands anyway, along with equipment that purges gases and cools and heats the shuttle on the ground, thruster plugs and 60 workers from the Kennedy Space Center.
+
+"As we get closer, we'll have much more certainty on what we're really faced with," said entry director Norm Knight, who will direct the landing.
+
+The first landing opportunity was set for 3:56 p.m. EST at Kennedy Space Center. Other opportunities were 1 1/2 hours later at all three sites, followed by opportunities at Edwards and White Sands 1 1/2 hours after that. NASA managers were considering a last try at 8:36 p.m. ET at Edwards.
+
+NASA has seven more opportunities to land the shuttle on Saturday.
+
+Discovery originally had been scheduled to land on Thursday, but the flight was extended to allow a fourth spacewalk to fold up an accordion-like solar array on the space station. </p>
     <h1>The Minefield</h1>
     <p>To provide basic HTML examples for testing LSR navigation in Firefox 3.0 documents</p>
     
@@ -17,6 +41,29 @@
       <li><a href="ria.html">Rich Internet Applications</a></li>
       <li><a href="navbylandmark.html">Navigation By Landmark</a></li>
     </ul>
+<p>
+HOUSTON, Texas (AP) -- NASA managers cleared Discovery to return home Friday, planning for a possible touchdown in New Mexico for only the second time in space shuttle history because of bad weather on both coasts.
 
+As the crew woke up to Christmas music Friday morning, they still didn't know where the spacecraft would touch down.
+
+"I have a lot of things to worry about on this flight that I can control, and the weather is something I can't," Discovery commander Mark Polansky told reporters from space. "I'm ready to land at any of the three sites."
+
+Discovery needs to be on the ground Saturday or it could run out of the fuel that powers its electrical system.
+
+NASA normally has more time for the landing, but the astronauts spent an extra day at the international space station this week to work on a stubborn solar array.
+
+Rain and clouds were forecast during the shuttle's first landing opportunity Friday afternoon at Kennedy Space Center in Florida, and crosswinds were expected at NASA's next-best option, Edwards Air Force Base in California's Mojave Desert.
+
+The third option, White Sands Space Harbor in New Mexico, hasn't been used for a shuttle landing in 24 years, and in that landing, sand on the runway contaminated the orbiter, and the brakes were damaged. It isn't normally equipped to service the shuttles, either.
+
+NASA managers hoped the weather would clear at one of the favored sites by the first landing opportunity, but they shipped a crane to White Sands anyway, along with equipment that purges gases and cools and heats the shuttle on the ground, thruster plugs and 60 workers from the Kennedy Space Center.
+
+"As we get closer, we'll have much more certainty on what we're really faced with," said entry director Norm Knight, who will direct the landing.
+
+The first landing opportunity was set for 3:56 p.m. EST at Kennedy Space Center. Other opportunities were 1 1/2 hours later at all three sites, followed by opportunities at Edwards and White Sands 1 1/2 hours after that. NASA managers were considering a last try at 8:36 p.m. ET at Edwards.
+
+NASA has seven more opportunities to land the shuttle on Saturday.
+
+Discovery originally had been scheduled to land on Thursday, but the flight was extended to allow a fourth spacewalk to fold up an accordion-like solar array on the space station. </p>
   </body>
 </html>
Index: src/Perks/ReviewPerk.py
===================================================================
--- src/Perks/ReviewPerk.py	(revision 757)
+++ src/Perks/ReviewPerk.py	(working copy)
@@ -189,9 +189,13 @@
     # respect if the skipping flag has already been set
     skipped = self.getTempVal('has skipped')
     self.setTempVal('has skipped', skipped or False)
-    
+    # search for all nodes when peeking, otherwise use user setting
+    if self.peek:
+      onlyvisible = False
+    else:
+      onlyvisible = self.perk_state.OnlyVisible
     for por in self.iterNextItems(wrap=True, 
-                                  only_visible=self.perk_state.OnlyVisible):
+                                  only_visible=onlyvisible):
       # check if we can stop on this item
       self.doTask('review should skip', por=por, peek=self.peek)
       if not self.getTempVal('should skip'):
@@ -218,9 +222,14 @@
     # respect if the skipping flag has already been set
     skipped = self.getTempVal('has skipped')
     self.setTempVal('has skipped', skipped or False)
+    # search for all nodes when peeking, otherwise use user setting
+    if self.peek:
+      onlyvisible = False
+    else:
+      onlyvisible = self.perk_state.OnlyVisible
     # try to get the previous item
     for por in self.iterPrevItems(wrap=True,
-                                  only_visible=self.perk_state.OnlyVisible):
+                                  only_visible=onlyvisible):
       # check if we can stop on this item
       self.doTask('review should skip', por=por, peek=self.peek)
       if not self.getTempVal('should skip'):
Index: src/Perks/FirefoxPerk.py
===================================================================
--- src/Perks/FirefoxPerk.py	(revision 757)
+++ src/Perks/FirefoxPerk.py	(working copy)
@@ -904,9 +904,16 @@
     next_por = self.getTempVal('peek')
     next_in_doc = self._isInDoc(next_por)
     
+    # moving caret programmatically scrolls screen and brings por into view.
+    # need to set the next item to account for lists
+    if self.getAnchorTaskId().find(' next ') > 0:
+      ni = self.getNextItem(por=next_por, wrap=True)
+    else:
+      ni = self.getPrevItem(por=next_por, wrap=True)
+    self.setAccCaret(por=ni)
+   
     # now determine whether we're 1) in doc to in doc, 2) out of doc to in doc,
     # 3) in doc to out of doc, or 4) out of doc to out of doc
-    
     # navigating within document or into the document (1 and 2)
     if next_in_doc:
       # check if the item should get the focus
@@ -947,8 +954,6 @@
       # execute the anchor, but do not let its immediate chains run too since
       # that would end up re-executing this task ad infinitum
       self.doTask(self.getAnchorTaskId(), chain=False)
-      # moving caret programmatically scrolls screen and brings por into view.
-      self.setAccCaret()
     return propagate
 
 class ReadReviewRole(Task.Task):
