<?xml version="1.0" encoding="UTF-8"?><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>Comments for Adobe Evangelists of Central PA</title>
	<atom:link href="http://www.cpmmug.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cpmmug.com</link>
	<description>Central PA Multimedia Users Blog</description>
	<pubDate>Wed, 10 Mar 2010 21:53:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>Comment on Should You Hire a Web Designer or a Web Developer for Your Website? by Jacklee</title>
		<link>http://www.cpmmug.com/general/should-you-hire-a-web-designer-or-a-web-developer-for-your-website/#comment-1998</link>
		<dc:creator>Jacklee</dc:creator>
		<pubDate>Mon, 01 Jun 2009 11:00:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.cpmmug.com/?p=13#comment-1998</guid>
		<description>Folks sure love their regular expressions…

The question was whether “every developer should know ___”. Notice that all of us said no on RIA platforms like Silverlight, despite the fact that some of us are really into Silverlight.

Also - why would you assume that we don’t know regular expressions? That’s a pretty condescending assumption. We’ve put the time into learning regular expressions, see that they’re a useful tool, and didn’t think that they made the cut for required, basic knowledge that every single web developer should know. Would every developer benefit from knowing assembly language? Sure! Is assembly language core, basic knowledge that every developer should put time into learning? Not in my book.

I’d rather web developers put that time into learning the HTML/CSS platform better. I’ve worked with a lot of web developers who were handy with a regex but couldn’t write cross-browser code or table-less layouts. That’s a mistake.

I do think people overrate the utility of regex’s. Having used regular expressions extensively in a custom CMS application, my personal experience is that they’re easy enough when you’re writing the application, but the maintenance and edge cases kill you. So in my opinion, they’re fine for things like e-mail validation, but pretty error prone for things like HTML manipulation (c.f. all the security vulnerabilities Jeff Atwood hit with StackOverflow’s HTML manipulation).</description>
		<content:encoded><![CDATA[<p>Folks sure love their regular expressions…</p>
<p>The question was whether “every developer should know ___”. Notice that all of us said no on RIA platforms like Silverlight, despite the fact that some of us are really into Silverlight.</p>
<p>Also - why would you assume that we don’t know regular expressions? That’s a pretty condescending assumption. We’ve put the time into learning regular expressions, see that they’re a useful tool, and didn’t think that they made the cut for required, basic knowledge that every single web developer should know. Would every developer benefit from knowing assembly language? Sure! Is assembly language core, basic knowledge that every developer should put time into learning? Not in my book.</p>
<p>I’d rather web developers put that time into learning the HTML/CSS platform better. I’ve worked with a lot of web developers who were handy with a regex but couldn’t write cross-browser code or table-less layouts. That’s a mistake.</p>
<p>I do think people overrate the utility of regex’s. Having used regular expressions extensively in a custom CMS application, my personal experience is that they’re easy enough when you’re writing the application, but the maintenance and edge cases kill you. So in my opinion, they’re fine for things like e-mail validation, but pretty error prone for things like HTML manipulation (c.f. all the security vulnerabilities Jeff Atwood hit with StackOverflow’s HTML manipulation).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Adobe GoLive Goes Dead by andrew c</title>
		<link>http://www.cpmmug.com/general/adobe-golive-goes-dead/#comment-1812</link>
		<dc:creator>andrew c</dc:creator>
		<pubDate>Tue, 05 May 2009 02:22:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.cpmmug.com/?p=11#comment-1812</guid>
		<description>Very nice?learned alot with this very simple tutorial.</description>
		<content:encoded><![CDATA[<p>Very nice?learned alot with this very simple tutorial.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Adobe Spry Tabbed Panels meets Sliding Door and CSS Sprites by Anders</title>
		<link>http://www.cpmmug.com/website-development/adobe-spry-tabbed-panels-meets-sliding-door-and-css-sprites/#comment-1452</link>
		<dc:creator>Anders</dc:creator>
		<pubDate>Tue, 17 Mar 2009 10:57:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.cpmmug.com/?p=5#comment-1452</guid>
		<description>This is for Spry 1.4 from what I can see. 

Dreamweaver CS4 has Spry 1.6.1 and it's not working with this fix. 
I could really need a solution for 1.6.1.

Spry 1.6.1 is also available for CS3 as a separate download.</description>
		<content:encoded><![CDATA[<p>This is for Spry 1.4 from what I can see. </p>
<p>Dreamweaver CS4 has Spry 1.6.1 and it&#8217;s not working with this fix.<br />
I could really need a solution for 1.6.1.</p>
<p>Spry 1.6.1 is also available for CS3 as a separate download.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Should You Hire a Web Designer or a Web Developer for Your Website? by Direct Response</title>
		<link>http://www.cpmmug.com/general/should-you-hire-a-web-designer-or-a-web-developer-for-your-website/#comment-1404</link>
		<dc:creator>Direct Response</dc:creator>
		<pubDate>Thu, 12 Mar 2009 17:31:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.cpmmug.com/?p=13#comment-1404</guid>
		<description>Every time i come here I am not dissapointed, nice post</description>
		<content:encoded><![CDATA[<p>Every time i come here I am not dissapointed, nice post</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Adobe GoLive Goes Dead by aSKer</title>
		<link>http://www.cpmmug.com/general/adobe-golive-goes-dead/#comment-1380</link>
		<dc:creator>aSKer</dc:creator>
		<pubDate>Tue, 10 Mar 2009 15:52:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.cpmmug.com/?p=11#comment-1380</guid>
		<description>Wow! Thank you! I always wanted to write in one of my sites something like that.</description>
		<content:encoded><![CDATA[<p>Wow! Thank you! I always wanted to write in one of my sites something like that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Adobe Labs and New Betas by julie</title>
		<link>http://www.cpmmug.com/general/adobe-labs-and-new-betas/#comment-1301</link>
		<dc:creator>julie</dc:creator>
		<pubDate>Wed, 04 Mar 2009 01:19:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.cpmmug.com/?p=12#comment-1301</guid>
		<description>I wanted to comment and thank the author, good stuff</description>
		<content:encoded><![CDATA[<p>I wanted to comment and thank the author, good stuff</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Should You Hire a Web Designer or a Web Developer for Your Website? by henry</title>
		<link>http://www.cpmmug.com/general/should-you-hire-a-web-designer-or-a-web-developer-for-your-website/#comment-1300</link>
		<dc:creator>henry</dc:creator>
		<pubDate>Wed, 04 Mar 2009 01:17:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.cpmmug.com/?p=13#comment-1300</guid>
		<description>nice tuts, is there a section to just these methods?</description>
		<content:encoded><![CDATA[<p>nice tuts, is there a section to just these methods?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Photoshop Tricks, Tips and Tantalizing Tutorials by nice review</title>
		<link>http://www.cpmmug.com/photoshop/photoshop-tricks-tips-and-tantalizing-tutorials/#comment-1299</link>
		<dc:creator>nice review</dc:creator>
		<pubDate>Wed, 04 Mar 2009 01:16:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.cpmmug.com/?p=14#comment-1299</guid>
		<description>I wanted to comment and thank the author, good stuff</description>
		<content:encoded><![CDATA[<p>I wanted to comment and thank the author, good stuff</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Adobe Spry Tabbed Panels meets Sliding Door and CSS Sprites by cpetrou.com</title>
		<link>http://www.cpmmug.com/website-development/adobe-spry-tabbed-panels-meets-sliding-door-and-css-sprites/#comment-748</link>
		<dc:creator>cpetrou.com</dc:creator>
		<pubDate>Mon, 17 Nov 2008 22:05:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.cpmmug.com/?p=5#comment-748</guid>
		<description>Here is a working example...
http://www.allensmemorylane.com/contact/

Here is the basic HTML...

   
     
       &lt;a href="#tab1" rel="nofollow"&gt;Tab 1&lt;/a&gt;
       &lt;a href="#tab2" rel="nofollow"&gt;Tab 2&lt;/a&gt;
       &lt;a href="#tab3" rel="nofollow"&gt;Tab 3&lt;/a&gt;
     
     
       Content for Tab 1.
       Content for Tab 2.
       Content for Tab 3.
     
   


Here is the basic CSS to place after the Spry / Dreamweaver generated CSS...

/* BEGIN: Spry Horizontal Tabbed Panels meets Sliding Door and CSS Sprites */
/* Revision by Craig Malcolm Petrou of cpetrou.com */
.TabbedPanels {
       margin: 10px 0 5px 0;
}
.TabbedPanelsTab {
       font-weight: bold;
       font-size: 100%;
       background-color: #FFF;
       border: solid 0 #FFF;
}
.TabbedPanelsTabHover {
       background-color: #FFF;
}
.TabbedPanelsTabSelected {
       background-color: #FFF;
       border-bottom: 1px solid #FFF;
       position: relative;
}
.TabbedPanelsContentGroup {
       background-color: #FFF;
}
ul.TabbedPanelsTabGroup a  {
       display: block;
}
ul.TabbedPanelsTabGroup li.TabbedPanelsTab {
 background: url(/images/tabbedpanels.gif) no-repeat 0 0;
 margin: 0 0 0 -1px;
 padding: 0 0 0 10px;
}
ul.TabbedPanelsTabGroup li.TabbedPanelsTab a {
 background: url(/images/tabbedpanels.gif) no-repeat 100% 0;
 padding: 7px 10px 5px 0;
}
ul.TabbedPanelsTabGroup li.TabbedPanelsTabSelected {
 background: url(/images/tabbedpanels.gif) no-repeat 0 -41px;
}
ul.TabbedPanelsTabGroup li.TabbedPanelsTabSelected a {
 background: url(/images/tabbedpanels.gif) no-repeat 100% -41px;
}
/* END: Spry Horizontal Tabbed Panels meets Sliding Door and CSS Sprites */

Let me know if this works for you.

--
Sincerely,
Craig Malcolm Petrou
craig@cpetrou.com
http://www.cpetrou.com</description>
		<content:encoded><![CDATA[<p>Here is a working example&#8230;<br />
<a href="http://www.allensmemorylane.com/contact/" rel="nofollow">http://www.allensmemorylane.com/contact/</a></p>
<p>Here is the basic HTML&#8230;</p>
<p>       <a href="#tab1" rel="nofollow">Tab 1</a><br />
       <a href="#tab2" rel="nofollow">Tab 2</a><br />
       <a href="#tab3" rel="nofollow">Tab 3</a></p>
<p>       Content for Tab 1.<br />
       Content for Tab 2.<br />
       Content for Tab 3.</p>
<p>Here is the basic CSS to place after the Spry / Dreamweaver generated CSS&#8230;</p>
<p>/* BEGIN: Spry Horizontal Tabbed Panels meets Sliding Door and CSS Sprites */<br />
/* Revision by Craig Malcolm Petrou of cpetrou.com */<br />
.TabbedPanels {<br />
       margin: 10px 0 5px 0;<br />
}<br />
.TabbedPanelsTab {<br />
       font-weight: bold;<br />
       font-size: 100%;<br />
       background-color: #FFF;<br />
       border: solid 0 #FFF;<br />
}<br />
.TabbedPanelsTabHover {<br />
       background-color: #FFF;<br />
}<br />
.TabbedPanelsTabSelected {<br />
       background-color: #FFF;<br />
       border-bottom: 1px solid #FFF;<br />
       position: relative;<br />
}<br />
.TabbedPanelsContentGroup {<br />
       background-color: #FFF;<br />
}<br />
ul.TabbedPanelsTabGroup a  {<br />
       display: block;<br />
}<br />
ul.TabbedPanelsTabGroup li.TabbedPanelsTab {<br />
 background: url(/images/tabbedpanels.gif) no-repeat 0 0;<br />
 margin: 0 0 0 -1px;<br />
 padding: 0 0 0 10px;<br />
}<br />
ul.TabbedPanelsTabGroup li.TabbedPanelsTab a {<br />
 background: url(/images/tabbedpanels.gif) no-repeat 100% 0;<br />
 padding: 7px 10px 5px 0;<br />
}<br />
ul.TabbedPanelsTabGroup li.TabbedPanelsTabSelected {<br />
 background: url(/images/tabbedpanels.gif) no-repeat 0 -41px;<br />
}<br />
ul.TabbedPanelsTabGroup li.TabbedPanelsTabSelected a {<br />
 background: url(/images/tabbedpanels.gif) no-repeat 100% -41px;<br />
}<br />
/* END: Spry Horizontal Tabbed Panels meets Sliding Door and CSS Sprites */</p>
<p>Let me know if this works for you.</p>
<p>&#8211;<br />
Sincerely,<br />
Craig Malcolm Petrou<br />
<a href="mailto:craig@cpetrou.com">craig@cpetrou.com</a><br />
<a href="http://www.cpetrou.com" rel="nofollow">http://www.cpetrou.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Adobe Spry Tabbed Panels meets Sliding Door and CSS Sprites by Nish</title>
		<link>http://www.cpmmug.com/website-development/adobe-spry-tabbed-panels-meets-sliding-door-and-css-sprites/#comment-746</link>
		<dc:creator>Nish</dc:creator>
		<pubDate>Mon, 17 Nov 2008 20:19:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.cpmmug.com/?p=5#comment-746</guid>
		<description>this is exactly what I've been looking for but I can't seem to get it to work. What did I do wrong? Please help! Everytime I click a tab in the preview IE won't show the page.
thanks in advance.

here is the html:




Untitled Document






  
     &lt;a href="”#Tab1?" rel="nofollow"&gt;instructor &lt;/a&gt;
    &lt;a href="”#Tab2?" rel="nofollow"&gt;events&lt;/a&gt;
    &lt;a href="”#Tab3?" rel="nofollow"&gt; school news &lt;/a&gt;
  
  
    
      Teacher-to-Teacher Forum
      Teaching Tips/Lesson Plans
      Instructor Scholarships and Awards
      Instructor Professional Development
      Student Scholarship
    
    
      event 1
      event 2
      event 3
    
    
      school news jfdksafjdksaj
      aksjfd;asjfdk;sajfkd
      jkdfjsa;jfkdsaj;fjdksajfkd;sjakfjdas;
      jdka;jfdka;jfkdja;fjdkajsfjdas;jfd;ajf
      
    
  








and the CSS:
@charset "UTF-8";

/* SpryTabbedPanels.css - Revision: Spry Preview Release 1.4 */

/* Copyright (c) 2006. Adobe Systems Incorporated. All rights reserved. */

/* Horizontal Tabbed Panels
 *
 * The default style for a TabbedPanels widget places all tab buttons
 * (left aligned) above the content panel.
 */

/* This is the selector for the main TabbedPanels container. For our
 * default style, this container does not contribute anything visually,
 * but it is floated left to make sure that any floating or clearing done
 * with any of its child elements are contained completely within the
 * TabbedPanels container, to minimize any impact or undesireable
 * interaction with other floated elements on the page that may be used
 * for layout.
 *
 * If you want to constrain the width of the TabbedPanels widget, set a
 * width on the TabbedPanels container. By default, the TabbedPanels widget
 * expands horizontally to fill up available space.
 *
 * The name of the class ("TabbedPanels") used in this selector is not
 * necessary to make the widget function. You can use any class name you
 * want to style the TabbedPanels container.
 */
.TabbedPanels {
	margin: 0px;
	padding: 0px;
	float: left;
	clear: none;
	width: 100%; /* IE Hack to force proper layout when preceded by a paragraph. (hasLayout Bug)*/
}

/* This is the selector for the TabGroup. The TabGroup container houses
 * all of the tab buttons for each tabbed panel in the widget. This container
 * does not contribute anything visually to the look of the widget for our
 * default style.
 *
 * The name of the class ("TabbedPanelsTabGroup") used in this selector is not
 * necessary to make the widget function. You can use any class name you
 * want to style the TabGroup container.
 */
.TabbedPanelsTabGroup {
	margin: 0px;
	padding: 0px;
}

/* This is the selector for the TabbedPanelsTab. This container houses
 * the title for the panel. This is also the tab "button" that the user clicks
 * on to activate the corresponding content panel so that it appears on top
 * of the other tabbed panels contained in the widget.
 *
 * For our default style, each tab is positioned relatively 1 pixel down from
 * where it wold normally render. This allows each tab to overlap the content
 * panel that renders below it. Each tab is rendered with a 1 pixel bottom
 * border that has a color that matches the top border of the current content
 * panel. This gives the appearance that the tab is being drawn behind the
 * content panel.
 *
 * The name of the class ("TabbedPanelsTab") used in this selector is not
 * necessary to make the widget function. You can use any class name you want
 * to style this tab container.
 */
.TabbedPanelsTab {
	position: relative;
	top: 1px;
	float: left;
	padding: 4px 10px;
	margin: 0px 1px 0px 0px;
	font: bold 0.7em sans-serif;
	background-color: #DDD;
	list-style: none;
	border-left: solid 1px #CCC;
	border-bottom: solid 1px #999;
	border-top: solid 1px #999;
	border-right: solid 1px #999;
	-moz-user-select: none;
	-khtml-user-select: none;
	cursor: pointer;
}

/* This selector is an example of how to change the appearnce of a tab button
 * container as the mouse enters it. The class "TabbedPanelsTabHover" is
 * programatically added and removed from the tab element as the mouse enters
 * and exits the container.
 */
.TabbedPanelsTabHover {
	background-color: #CCC;
}

/* This selector is an example of how to change the appearance of a tab button
 * container after the user has clicked on it to activate a content panel.
 * The class "TabbedPanelsTabSelected" is programatically added and removed
 * from the tab element as the user clicks on the tab button containers in
 * the widget.
 *
 * As mentioned above, for our default style, tab buttons are positioned
 * 1 pixel down from where it would normally render. When the tab button is
 * selected, we change its bottom border to match the background color of the
 * content panel so that it looks like the tab is part of the content panel.
 */
.TabbedPanelsTabSelected {
	background-color: #EEE;
	border-bottom: 1px solid #EEE;
}

/* This selector is an example of how to make a link inside of a tab button
 * look like normal text. Users may want to use links inside of a tab button
 * so that when it gets focus, the text *inside* the tab button gets a focus
 * ring around it, instead of the focus ring around the entire tab.
 */
.TabbedPanelsTab a {
	color: black;
	text-decoration: none;
}

/* This is the selector for the ContentGroup. The ContentGroup container houses
 * all of the content panels for each tabbed panel in the widget. For our
 * default style, this container provides the background color and borders that
 * surround the content.
 *
 * The name of the class ("TabbedPanelsContentGroup") used in this selector is
 * not necessary to make the widget function. You can use any class name you
 * want to style the ContentGroup container.
 */
.TabbedPanelsContentGroup {
	clear: both;
	border-left: solid 1px #CCC;
	border-bottom: solid 1px #CCC;
	border-top: solid 1px #999;
	border-right: solid 1px #999;
	background-color: #EEE;
}

/* This is the selector for the Content panel. The Content panel holds the
 * content for a single tabbed panel. For our default style, this container
 * provides some padding, so that the content is not pushed up against the
 * widget borders.
 *
 * The name of the class ("TabbedPanelsContent") used in this selector is
 * not necessary to make the widget function. You can use any class name you
 * want to style the Content container.
 */
.TabbedPanelsContent {
	padding: 4px;
}

/* This selector is an example of how to change the appearnce of the currently
 * active container panel. The class "TabbedPanelsContentVisible" is
 * programatically added and removed from the content element as the panel
 * is activated/deactivated.
 */
.TabbedPanelsContentVisible {
}

/* Vertical Tabbed Panels
 *
 * The following rules override some of the default rules above so that the
 * TabbedPanels widget renders with its tab buttons along the left side of
 * the currently active content panel.
 *
 * With the rules defined below, the only change that will have to be made
 * to switch a horizontal tabbed panels widget to a vertical tabbed panels
 * widget, is to use the "VTabbedPanels" class on the top-level widget
 * container element, instead of "TabbedPanels".
 */

/* This selector floats the TabGroup so that the tab buttons it contains
 * render to the left of the active content panel. A border is drawn around
 * the group container to make it look like a list container.
 */
.VTabbedPanels .TabbedPanelsTabGroup {
	float: left;
	width: 10em;
	height: 20em;
	background-color: #EEE;
	position: relative;
	border-top: solid 1px #999;
	border-right: solid 1px #999;
	border-left: solid 1px #CCC;
	border-bottom: solid 1px #CCC;
}

/* This selector disables the float property that is placed on each tab button
 * by the default TabbedPanelsTab selector rule above. It also draws a bottom
 * border for the tab. The tab button will get its left and right border from
 * the TabGroup, and its top border from the TabGroup or tab button above it.
 */
.VTabbedPanels .TabbedPanelsTab {
	float: none;
	margin: 0px;
	border-top: none;
	border-left: none;
	border-right: none;
}

/* This selector disables the float property that is placed on each tab button
 * by the default TabbedPanelsTab selector rule above. It also draws a bottom
 * border for the tab. The tab button will get its left and right border from
 * the TabGroup, and its top border from the TabGroup or tab button above it.
 */
.VTabbedPanels .TabbedPanelsTabSelected {
	background-color: #EEE;
	border-bottom: solid 1px #999;
}

/* This selector floats the content panels for the widget so that they
 * render to the right of the tabbed buttons.
 */
.VTabbedPanels .TabbedPanelsContentGroup {
	clear: none;
	float: left;
	padding: 0px;
	width: 30em;
	height: 20em;
}

/* BEGIN: Spry Horizontal Tabbed Panels meets Sliding Door and CSS Sprites */
/* Revision by Craig Malcolm Petrou of cpetrou.com */
.TabbedPanels {
margin: 0 5px 20px 0;
width: 570px;
}
.TabbedPanelsContent {
background-position: bottom;
padding: 9px;
}
.TabbedPanelsContentGroup {
background-color: #FFF;
border: 1px solid #4E4087;
}
.TabbedPanelsTab {
background-color: #FFF;
border: solid 0 #FFF;
font: bold 90% “Trebuchet MS”, Trebuchet, Verdana, Arial, Helvetica, sans-serif;
text-align: center;
height: 30px;
}
.TabbedPanelsTabHover {
background-color: #FFF;
}
.TabbedPanelsTabSelected {
background-color: #FFF;
}
ul.TabbedPanelsTabGroup a {
display: block;
}
ul.TabbedPanelsTabGroup li.TabbedPanelsTab {
background: url(/images/spryTabbedPanels.gif) no-repeat 0 0;
margin: 0 0 0 -1px;
padding: 0 0 0 10px;
}
ul.TabbedPanelsTabGroup li.TabbedPanelsTab a {
background: url(/images/spryTabbedPanels.gif) no-repeat 100% 0;
padding: 7px 10px 5px 0;
}
ul.TabbedPanelsTabGroup li.TabbedPanelsTabSelected {
background: url(/images/spryTabbedPanels.gif) no-repeat 0 -31px;
}
ul.TabbedPanelsTabGroup li.TabbedPanelsTabSelected a {
background: url(/images/spryTabbedPanels.gif) no-repeat 100% -31px;
}
/* END: Spry Horizontal Tabbed Panels meets Sliding Door and CSS Sprites */</description>
		<content:encoded><![CDATA[<p>this is exactly what I&#8217;ve been looking for but I can&#8217;t seem to get it to work. What did I do wrong? Please help! Everytime I click a tab in the preview IE won&#8217;t show the page.<br />
thanks in advance.</p>
<p>here is the html:</p>
<p>Untitled Document</p>
<p>     <a href="”#Tab1?" rel="nofollow">instructor </a><br />
    <a href="”#Tab2?" rel="nofollow">events</a><br />
    <a href="”#Tab3?" rel="nofollow"> school news </a></p>
<p>      Teacher-to-Teacher Forum<br />
      Teaching Tips/Lesson Plans<br />
      Instructor Scholarships and Awards<br />
      Instructor Professional Development<br />
      Student Scholarship</p>
<p>      event 1<br />
      event 2<br />
      event 3</p>
<p>      school news jfdksafjdksaj<br />
      aksjfd;asjfdk;sajfkd<br />
      jkdfjsa;jfkdsaj;fjdksajfkd;sjakfjdas;<br />
      jdka;jfdka;jfkdja;fjdkajsfjdas;jfd;ajf</p>
<p>and the CSS:<br />
@charset &#8220;UTF-8&#8243;;</p>
<p>/* SpryTabbedPanels.css - Revision: Spry Preview Release 1.4 */</p>
<p>/* Copyright (c) 2006. Adobe Systems Incorporated. All rights reserved. */</p>
<p>/* Horizontal Tabbed Panels<br />
 *<br />
 * The default style for a TabbedPanels widget places all tab buttons<br />
 * (left aligned) above the content panel.<br />
 */</p>
<p>/* This is the selector for the main TabbedPanels container. For our<br />
 * default style, this container does not contribute anything visually,<br />
 * but it is floated left to make sure that any floating or clearing done<br />
 * with any of its child elements are contained completely within the<br />
 * TabbedPanels container, to minimize any impact or undesireable<br />
 * interaction with other floated elements on the page that may be used<br />
 * for layout.<br />
 *<br />
 * If you want to constrain the width of the TabbedPanels widget, set a<br />
 * width on the TabbedPanels container. By default, the TabbedPanels widget<br />
 * expands horizontally to fill up available space.<br />
 *<br />
 * The name of the class (&#8221;TabbedPanels&#8221;) used in this selector is not<br />
 * necessary to make the widget function. You can use any class name you<br />
 * want to style the TabbedPanels container.<br />
 */<br />
.TabbedPanels {<br />
	margin: 0px;<br />
	padding: 0px;<br />
	float: left;<br />
	clear: none;<br />
	width: 100%; /* IE Hack to force proper layout when preceded by a paragraph. (hasLayout Bug)*/<br />
}</p>
<p>/* This is the selector for the TabGroup. The TabGroup container houses<br />
 * all of the tab buttons for each tabbed panel in the widget. This container<br />
 * does not contribute anything visually to the look of the widget for our<br />
 * default style.<br />
 *<br />
 * The name of the class (&#8221;TabbedPanelsTabGroup&#8221;) used in this selector is not<br />
 * necessary to make the widget function. You can use any class name you<br />
 * want to style the TabGroup container.<br />
 */<br />
.TabbedPanelsTabGroup {<br />
	margin: 0px;<br />
	padding: 0px;<br />
}</p>
<p>/* This is the selector for the TabbedPanelsTab. This container houses<br />
 * the title for the panel. This is also the tab &#8220;button&#8221; that the user clicks<br />
 * on to activate the corresponding content panel so that it appears on top<br />
 * of the other tabbed panels contained in the widget.<br />
 *<br />
 * For our default style, each tab is positioned relatively 1 pixel down from<br />
 * where it wold normally render. This allows each tab to overlap the content<br />
 * panel that renders below it. Each tab is rendered with a 1 pixel bottom<br />
 * border that has a color that matches the top border of the current content<br />
 * panel. This gives the appearance that the tab is being drawn behind the<br />
 * content panel.<br />
 *<br />
 * The name of the class (&#8221;TabbedPanelsTab&#8221;) used in this selector is not<br />
 * necessary to make the widget function. You can use any class name you want<br />
 * to style this tab container.<br />
 */<br />
.TabbedPanelsTab {<br />
	position: relative;<br />
	top: 1px;<br />
	float: left;<br />
	padding: 4px 10px;<br />
	margin: 0px 1px 0px 0px;<br />
	font: bold 0.7em sans-serif;<br />
	background-color: #DDD;<br />
	list-style: none;<br />
	border-left: solid 1px #CCC;<br />
	border-bottom: solid 1px #999;<br />
	border-top: solid 1px #999;<br />
	border-right: solid 1px #999;<br />
	-moz-user-select: none;<br />
	-khtml-user-select: none;<br />
	cursor: pointer;<br />
}</p>
<p>/* This selector is an example of how to change the appearnce of a tab button<br />
 * container as the mouse enters it. The class &#8220;TabbedPanelsTabHover&#8221; is<br />
 * programatically added and removed from the tab element as the mouse enters<br />
 * and exits the container.<br />
 */<br />
.TabbedPanelsTabHover {<br />
	background-color: #CCC;<br />
}</p>
<p>/* This selector is an example of how to change the appearance of a tab button<br />
 * container after the user has clicked on it to activate a content panel.<br />
 * The class &#8220;TabbedPanelsTabSelected&#8221; is programatically added and removed<br />
 * from the tab element as the user clicks on the tab button containers in<br />
 * the widget.<br />
 *<br />
 * As mentioned above, for our default style, tab buttons are positioned<br />
 * 1 pixel down from where it would normally render. When the tab button is<br />
 * selected, we change its bottom border to match the background color of the<br />
 * content panel so that it looks like the tab is part of the content panel.<br />
 */<br />
.TabbedPanelsTabSelected {<br />
	background-color: #EEE;<br />
	border-bottom: 1px solid #EEE;<br />
}</p>
<p>/* This selector is an example of how to make a link inside of a tab button<br />
 * look like normal text. Users may want to use links inside of a tab button<br />
 * so that when it gets focus, the text *inside* the tab button gets a focus<br />
 * ring around it, instead of the focus ring around the entire tab.<br />
 */<br />
.TabbedPanelsTab a {<br />
	color: black;<br />
	text-decoration: none;<br />
}</p>
<p>/* This is the selector for the ContentGroup. The ContentGroup container houses<br />
 * all of the content panels for each tabbed panel in the widget. For our<br />
 * default style, this container provides the background color and borders that<br />
 * surround the content.<br />
 *<br />
 * The name of the class (&#8221;TabbedPanelsContentGroup&#8221;) used in this selector is<br />
 * not necessary to make the widget function. You can use any class name you<br />
 * want to style the ContentGroup container.<br />
 */<br />
.TabbedPanelsContentGroup {<br />
	clear: both;<br />
	border-left: solid 1px #CCC;<br />
	border-bottom: solid 1px #CCC;<br />
	border-top: solid 1px #999;<br />
	border-right: solid 1px #999;<br />
	background-color: #EEE;<br />
}</p>
<p>/* This is the selector for the Content panel. The Content panel holds the<br />
 * content for a single tabbed panel. For our default style, this container<br />
 * provides some padding, so that the content is not pushed up against the<br />
 * widget borders.<br />
 *<br />
 * The name of the class (&#8221;TabbedPanelsContent&#8221;) used in this selector is<br />
 * not necessary to make the widget function. You can use any class name you<br />
 * want to style the Content container.<br />
 */<br />
.TabbedPanelsContent {<br />
	padding: 4px;<br />
}</p>
<p>/* This selector is an example of how to change the appearnce of the currently<br />
 * active container panel. The class &#8220;TabbedPanelsContentVisible&#8221; is<br />
 * programatically added and removed from the content element as the panel<br />
 * is activated/deactivated.<br />
 */<br />
.TabbedPanelsContentVisible {<br />
}</p>
<p>/* Vertical Tabbed Panels<br />
 *<br />
 * The following rules override some of the default rules above so that the<br />
 * TabbedPanels widget renders with its tab buttons along the left side of<br />
 * the currently active content panel.<br />
 *<br />
 * With the rules defined below, the only change that will have to be made<br />
 * to switch a horizontal tabbed panels widget to a vertical tabbed panels<br />
 * widget, is to use the &#8220;VTabbedPanels&#8221; class on the top-level widget<br />
 * container element, instead of &#8220;TabbedPanels&#8221;.<br />
 */</p>
<p>/* This selector floats the TabGroup so that the tab buttons it contains<br />
 * render to the left of the active content panel. A border is drawn around<br />
 * the group container to make it look like a list container.<br />
 */<br />
.VTabbedPanels .TabbedPanelsTabGroup {<br />
	float: left;<br />
	width: 10em;<br />
	height: 20em;<br />
	background-color: #EEE;<br />
	position: relative;<br />
	border-top: solid 1px #999;<br />
	border-right: solid 1px #999;<br />
	border-left: solid 1px #CCC;<br />
	border-bottom: solid 1px #CCC;<br />
}</p>
<p>/* This selector disables the float property that is placed on each tab button<br />
 * by the default TabbedPanelsTab selector rule above. It also draws a bottom<br />
 * border for the tab. The tab button will get its left and right border from<br />
 * the TabGroup, and its top border from the TabGroup or tab button above it.<br />
 */<br />
.VTabbedPanels .TabbedPanelsTab {<br />
	float: none;<br />
	margin: 0px;<br />
	border-top: none;<br />
	border-left: none;<br />
	border-right: none;<br />
}</p>
<p>/* This selector disables the float property that is placed on each tab button<br />
 * by the default TabbedPanelsTab selector rule above. It also draws a bottom<br />
 * border for the tab. The tab button will get its left and right border from<br />
 * the TabGroup, and its top border from the TabGroup or tab button above it.<br />
 */<br />
.VTabbedPanels .TabbedPanelsTabSelected {<br />
	background-color: #EEE;<br />
	border-bottom: solid 1px #999;<br />
}</p>
<p>/* This selector floats the content panels for the widget so that they<br />
 * render to the right of the tabbed buttons.<br />
 */<br />
.VTabbedPanels .TabbedPanelsContentGroup {<br />
	clear: none;<br />
	float: left;<br />
	padding: 0px;<br />
	width: 30em;<br />
	height: 20em;<br />
}</p>
<p>/* BEGIN: Spry Horizontal Tabbed Panels meets Sliding Door and CSS Sprites */<br />
/* Revision by Craig Malcolm Petrou of cpetrou.com */<br />
.TabbedPanels {<br />
margin: 0 5px 20px 0;<br />
width: 570px;<br />
}<br />
.TabbedPanelsContent {<br />
background-position: bottom;<br />
padding: 9px;<br />
}<br />
.TabbedPanelsContentGroup {<br />
background-color: #FFF;<br />
border: 1px solid #4E4087;<br />
}<br />
.TabbedPanelsTab {<br />
background-color: #FFF;<br />
border: solid 0 #FFF;<br />
font: bold 90% “Trebuchet MS”, Trebuchet, Verdana, Arial, Helvetica, sans-serif;<br />
text-align: center;<br />
height: 30px;<br />
}<br />
.TabbedPanelsTabHover {<br />
background-color: #FFF;<br />
}<br />
.TabbedPanelsTabSelected {<br />
background-color: #FFF;<br />
}<br />
ul.TabbedPanelsTabGroup a {<br />
display: block;<br />
}<br />
ul.TabbedPanelsTabGroup li.TabbedPanelsTab {<br />
background: url(/images/spryTabbedPanels.gif) no-repeat 0 0;<br />
margin: 0 0 0 -1px;<br />
padding: 0 0 0 10px;<br />
}<br />
ul.TabbedPanelsTabGroup li.TabbedPanelsTab a {<br />
background: url(/images/spryTabbedPanels.gif) no-repeat 100% 0;<br />
padding: 7px 10px 5px 0;<br />
}<br />
ul.TabbedPanelsTabGroup li.TabbedPanelsTabSelected {<br />
background: url(/images/spryTabbedPanels.gif) no-repeat 0 -31px;<br />
}<br />
ul.TabbedPanelsTabGroup li.TabbedPanelsTabSelected a {<br />
background: url(/images/spryTabbedPanels.gif) no-repeat 100% -31px;<br />
}<br />
/* END: Spry Horizontal Tabbed Panels meets Sliding Door and CSS Sprites */</p>
]]></content:encoded>
	</item>
</channel>
</rss>
