For scrolling wrap it in SPRememberScroll tag.

http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.webcontrols.sprememberscroll.aspx

Regards

Paul Turner
Practice Lead - SharePoint
SMS Management & Technology

M 0412 748 168
paul.tur...@smsmt.com<mailto:paul.tur...@smsmt.com>
www.smsmt.com<http://www.smsmt.com/>
About SMS: Innovation House, Technology Park, Mawson Lakes Boulevard, Mawson 
Lakes SA 5095
SMS Management & Technology (SMS) [ASX:SMX] is Australia's largest publicly 
listed Management Services company. We solve complex problems and transform 
business through Consulting, Technology and Systems Integration
P please consider the environment before printing this email

________________________________
From: ozmoss-boun...@ozmoss.com [ozmoss-boun...@ozmoss.com] On Behalf Of Dan 
Sheedy [sheedy...@gmail.com]
Sent: Monday, 20 June 2011 10:31 AM
To: ozMOSS
Subject: Re: SP2010 Main Navigation problems - Keyboard accessibility and 
Flyouts [SEC=UNCLASSIFIED]

Hi Kathleen.

 1.  You can also use the css selector :focus to target the focussed element in 
the style sheet.

 2.  In 2010 there is a bit of js that sets the page hieght so it plays nice 
with the ribbon control. This could be a reason for your menu problems. This 
might be useful, http://kyleschaeffer.com/sharepoint/sharepoint-2010-scrolling/.

HTH.

On Mon, Jun 20, 2011 at 10:50 AM, Paul Noone 
<paul.no...@ceosyd.catholic.edu.au<mailto:paul.no...@ceosyd.catholic.edu.au>> 
wrote:
1) The main navigation menu cannot be accessed using a keyboard. In our 
situation, this is a deal breaker. When pressing the TAB key, if you watch the 
status bar at the bottom of the window, you can see that the URL is changing 
and it is working through the menu system, but there's no visual way of knowing 
that this is happening on the menu bar. In SP2007 this wasn't a problem.

Have you enabled Accessibility mode? If so, is the tab order still not working 
through the topnav?

[cid:image001.png@01CC2F37.EFC2CE90]

2) Menu flyouts do not centre themselves vertically on the screen. For example, 
if you roll over the bottom link on the navigation menu and it has a 
corresponding flyout, and if this flyout contains a long-ish set of links, the 
flyout will extend itself over the bottom of the screen, making it impossible 
for the user to access those links. In SP2007, the flyouts automatically 
re-positioned themselves to move up the screen in a situation like this, making 
all links accessible.

That would be a considerably large menu! As a workaround you could add a 
minimum-height and additional margin to the bottom of the placeholder to 
overcome this. It’s not perfect but it works until a fix is implemented.

I was hoping for improvements in this area, not degradation.

Tell me, are the flyout menus even visible when using IE8 or IE9 standards 
mode? The only solution I ever found for 2007 using the OOTB provider was to 
use IE8 Compat with IE7 standards.

[cid:image002.png@01CC2F37.EFC2CE90]

_______________________________________________
ozmoss mailing list
ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss



________________________________
NOTICE - This communication is intended only for the person or entity to which 
it is addressed and may contain confidential and/or privileged material. Any 
review, retransmission, dissemination or other use of, or taking any action in 
reliance on, this communication by persons or entities other than the intended 
recipient is prohibited. If you are not the intended recipient of this 
communication please delete and destroy all copies and telephone SMS Management 
& Technology on 1300 842 767 immediately. Any views expressed in this 
Communication are those of the individual sender, except where the sender 
specifically states them to be the views of SMS Management & Technology. Except 
as required by law, SMS Management & Technology does not represent, warrant 
and/or guarantee that the integrity of this communication has been maintained 
nor that the communication is free from errors, virus, interception or 
interference.

<<inline: image001.png>>

<<inline: image002.png>>

_______________________________________________
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

Reply via email to