<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.1-alpha-2539" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
		>
	<channel>
		<title>WordPress.com Forums &#187; Topic: Static Menu Tabs: Leaving the URL field blank in custom links?</title>
		<link>http://en.forums.wordpress.com/topic/static-menu-tabs-leaving-the-url-field-blank-in-custom-links</link>
		<description>WordPress.com Forums &#187; Topic: Static Menu Tabs: Leaving the URL field blank in custom links?</description>
		<language>en</language>
		<pubDate>Sun, 19 May 2013 14:52:22 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.1-alpha-2539</generator>
				<atom:link href="http://en.forums.wordpress.com/rss/topic/static-menu-tabs-leaving-the-url-field-blank-in-custom-links" rel="self" type="application/rss+xml" />

		<item>
			<title>newtownforbes on "Static Menu Tabs: Leaving the URL field blank in custom links?"</title>
			<link>http://en.forums.wordpress.com/topic/static-menu-tabs-leaving-the-url-field-blank-in-custom-links#post-707812</link>
			<pubDate>Wed, 28 Sep 2011 14:12:14 +0000</pubDate>
			<dc:creator>newtownforbes</dc:creator>
			<guid isPermaLink="false">707812@http://en.forums.wordpress.com/</guid>
			<description><![CDATA[<p>Thanks for the response. I didn't think the idea could have been original, but I couldn't find any previous mentions in the forum. Thanks for the pointer. :)</p>
<p>As a newbie, I'm surprised that this isn't documented in the menus support doc instead of the # method. Leaving a blank url just seems much 'cleaner'. As well as not having the dummy URL show up in the status bar, and the visual clue of the pointer changing to an I-bar, (as mentioned above), there are a few other minor advantages. For instance, clicking a # adds it to your browser history; jumps to the top of the page if you're scrolled down, moving the menus away from your mouse pointer; and highlights the # item clicked, even if you're still actually looking at a page that's not part of that menu. None of these, albeit minor issues, occur with a blank url.</p>
<p>I hope you get the staff to take notice sometime! :)
</p>
]]></description>
					</item>
		<item>
			<title>panaghiotisadam on "Static Menu Tabs: Leaving the URL field blank in custom links?"</title>
			<link>http://en.forums.wordpress.com/topic/static-menu-tabs-leaving-the-url-field-blank-in-custom-links#post-707774</link>
			<pubDate>Wed, 28 Sep 2011 12:37:08 +0000</pubDate>
			<dc:creator>panaghiotisadam</dc:creator>
			<guid isPermaLink="false">707774@http://en.forums.wordpress.com/</guid>
			<description><![CDATA[<p>I was the first to suggest this (when custom menus were still a novelty and worked in a few themes only):<br />
<a href="http://en.forums.wordpress.com/topic/category-drop-down-menu?replies=6#post-478269" rel="nofollow">http://en.forums.wordpress.com/topic/category-drop-down-menu?replies=6#post-478269</a></p>
<p>And I kept suggesting it since then. If I remember well, there was a thread where a staff member said you can <em>also</em> use the # method, which means they didn't object to the other way of doing it. But they may change their mind.</p>
<p>Can it be relied upon to work in future versions of WP? I don't think this question can be answered: WP updates things all the time, so you cannot know. The Support docs are also continually updated, but still they don't document everything. The # trick itself wasn't there from the start:<br />
<a href="http://web.archive.org/web/20101105124304/http://en.support.wordpress.com/menus/" rel="nofollow">http://web.archive.org/web/20101105124304/http://en.support.wordpress.com/menus/</a>
</p>
]]></description>
					</item>
		<item>
			<title>newtownforbes on "Static Menu Tabs: Leaving the URL field blank in custom links?"</title>
			<link>http://en.forums.wordpress.com/topic/static-menu-tabs-leaving-the-url-field-blank-in-custom-links#post-707690</link>
			<pubDate>Wed, 28 Sep 2011 09:12:10 +0000</pubDate>
			<dc:creator>newtownforbes</dc:creator>
			<guid isPermaLink="false">707690@http://en.forums.wordpress.com/</guid>
			<description><![CDATA[<p>Hello all :)</p>
<p>As per <a href="http://en.support.wordpress.com/menus/#adding-static-top-level-tabs">the custom menus support document</a>, I added a static top level tab to my menu, and it worked fine. As an experiment though, instead of using # as the URL in the custom link, I left it blank. As you can see on my blog under the 'Newtownforbes' menu item, it seems to work just as well as when using #, but with the added benefit of not showing up the <a href="http://blah/#" rel="nofollow">http://blah/#</a> URL in the status bar when you hover over it. (The cursor also changes from a finger pointer to a plain I-bar.) Basically the menu item becomes a plain non-clickable text field, which to my eyes is nicer than the # version. So my question is, is this behaviour supported and valid - i.e. can it be relied upon to work in future versions of WordPress - or is it a fabled 'undocumented feature'? :)
</p>
]]></description>
					</item>

	</channel>
</rss>
