<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Simon Steed&#039;s Blog About Stuff! &#187; css</title>
	<atom:link href="http://blog.xploiter.com/tag/css/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.xploiter.com</link>
	<description>i.e. anything interesting...</description>
	<lastBuildDate>Wed, 01 Sep 2010 11:15:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3308</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Detecting the Safari Browser to load scripts</title>
		<link>http://blog.xploiter.com/it/detecting-safari-browser-load-scripts/</link>
		<comments>http://blog.xploiter.com/it/detecting-safari-browser-load-scripts/#comments</comments>
		<pubDate>Mon, 02 Aug 2010 08:29:55 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[dynamic load]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[safari]]></category>
		<category><![CDATA[script]]></category>

		<guid isPermaLink="false">http://blog.xploiter.com/?p=356</guid>
		<description><![CDATA[I needed to detect if Safari was being used as there were some issues with styling on a website I was working upon, only on Mac Safari though!!!]]></description>
			<content:encoded><![CDATA[<p>I needed to detect if Safari was being used as there were some issues with styling on a website I was working upon, only on Mac Safari though!!!</p>
<p>The following code is what I use to detect safari and load the relevant script:</p>
<pre id="line1">&lt;script type="text/javascript"&gt;

	if(/Safari/.test(navigator.userAgent))
	{
 		//you are using safari, or at least you CLAIM to be
		document.write('&lt;link type="text/css" media="screen" rel="stylesheet" href="/css/safari.css" title="example" /&gt;');
	}
	&lt;/script&gt;
</pre>
<p>Add in the <head></head> tags and set the path to the correct css file you wish to load. Same concept can be used to load javascript files.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.xploiter.com/it/detecting-safari-browser-load-scripts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Preparing an asp.net master page for print only view &#8211; stripping out css etc</title>
		<link>http://blog.xploiter.com/c-and-aspnet/preparing-aspnet-master-page-print-view-stripping-css/</link>
		<comments>http://blog.xploiter.com/c-and-aspnet/preparing-aspnet-master-page-print-view-stripping-css/#comments</comments>
		<pubDate>Wed, 07 Oct 2009 08:49:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[C# and ASP.Net]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[asp.net]]></category>
		<category><![CDATA[c#]]></category>
		<category><![CDATA[contentplaceholder]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[hiding]]></category>
		<category><![CDATA[master pages]]></category>

		<guid isPermaLink="false">http://blog.xploiter.com/?p=295</guid>
		<description><![CDATA[Searching google turned up nothing on this so did some digging in MSDN and worked out a method of disabling all the style sheets, javascript etc to produce a text only page: 1/ Add a content block to your master page &#8211; i&#8217;ve called mine &#8216;cssContentHolder&#8217; &#60;asp:contentplaceholder id=&#8221;cssContentHolder&#8221; runat=&#8221;server&#8221;&#62; &#60;link rel=&#8221;stylesheet&#8221; href=&#8221;css/master.css&#8221; type=&#8221;text/css&#8221; media=&#8221;all&#8221; /&#62;]]></description>
			<content:encoded><![CDATA[<p>Searching google turned up nothing on this so did some digging in MSDN and worked out a method of disabling all the style sheets, javascript etc to produce a text only page:</p>
<p>1/ Add a content block to your master page &#8211; i&#8217;ve called mine &#8216;cssContentHolder&#8217;</p>
<p>&lt;asp:contentplaceholder id=&#8221;cssContentHolder&#8221; runat=&#8221;server&#8221;&gt;<br />
&lt;link rel=&#8221;stylesheet&#8221; href=&#8221;css/master.css&#8221; type=&#8221;text/css&#8221; media=&#8221;all&#8221; /&gt;<br />
&lt;link href=&#8221;css/flyout.css&#8221; media=&#8221;screen&#8221; rel=&#8221;stylesheet&#8221; type=&#8221;text/css&#8221; /&gt;<br />
&lt;script src=&#8221;scripts/APIs/JQuery/JQuery-1.3.2.min.js&#8221; type=&#8221;text/javascript&#8221;&gt;&lt;/script&gt;<br />
&lt;script src=&#8221;scripts/APIs/JQuery/Plugins/jquery-ui-1.7.1.custom.min.js&#8221; type=&#8221;text/javascript&#8221;&gt;&lt;/script&gt;<br />
&lt;/asp:contentplaceholder&gt;</p>
<p>2/ In the markup, add a link button so the user can click it to remove the formatting</p>
<p>&lt;asp:LinkButton  PostBackUrl=&#8221;#&#8221; ID=&#8221;textLink&#8221;  runat=&#8221;server&#8221; Text=&#8221;Text Only Version&#8221; onclick=&#8221;textLink_Click&#8221; &gt;&lt;/asp:LinkButton&gt;</p>
<p>3/ In the code behind, create an event handler for the button and add the following code</p>
<p>protected void textLink_Click(object sender, EventArgs e)<br />
{<br />
bool Hidden = Page.Master.FindControl(&#8220;cssContentHolder&#8221;).Visible ;<br />
Page.Master.FindControl(&#8220;cssContentHolder&#8221;).Visible = !Hidden;<br />
if (Hidden)<br />
textLink.Text = &#8220;Switch to Graphical Version&#8221;;<br />
else<br />
textLink.Text = &#8220;Text Only Version&#8221;;<br />
}</p>
<p>That&#8217;s it. When you click on the link, you will perform a postback to the server, get the state of the control and show/hide accordingly. It will also change the text so you can click back again.</p>
<p>Simple when you know how!</p>
<p>Using Javascript, another method to remove all the CSS but not update any link text etc is to call the following function:</p>
<pre id="line1">function hideCSS(){
	if(document.getElementsByTagName){
		for(n=0;n&lt;document.getElementsByTagName("link").length;n++){
			if(document.getElementsByTagName("link")[n].getAttribute){
				if(document.getElementsByTagName("link")[n].getAttribute("rel").indexOf("stylesheet")!=-1){
					document.getElementsByTagName("link")[n].disabled="disabled"
					}
				}
			}
		}
	}</pre>
]]></content:encoded>
			<wfw:commentRss>http://blog.xploiter.com/c-and-aspnet/preparing-aspnet-master-page-print-view-stripping-css/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Developers issue death warrant for IE6 &#124; News &#124; TechRadar UK</title>
		<link>http://blog.xploiter.com/c-and-aspnet/developers-issue-death-warrant-for-ie6-news-techradar-uk/</link>
		<comments>http://blog.xploiter.com/c-and-aspnet/developers-issue-death-warrant-for-ie6-news-techradar-uk/#comments</comments>
		<pubDate>Tue, 24 Feb 2009 10:03:42 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[C# and ASP.Net]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[hacks]]></category>
		<category><![CDATA[ie6]]></category>
		<category><![CDATA[ie7]]></category>
		<category><![CDATA[kill internet explorer]]></category>

		<guid isPermaLink="false">http://blog.xploiter.com/?p=108</guid>
		<description><![CDATA[A campaign calling for the immediate death of Internet Explorer 6 is picking up pace, with a host of developers castigating the browser that &#8216;hindered the development of the web&#8217;. .net magazine is supporting a campaign to rid the world of IE6 – a browser that is still being used by a large proportion of]]></description>
			<content:encoded><![CDATA[<blockquote>
<p class="MsoNormal">A campaign calling for the immediate death of Internet Explorer 6 is picking up pace, with a host of developers castigating the browser that &#8216;hindered the development of the web&#8217;.</p>
<p class="MsoNormal">.<a href="http://www.netmag.co.uk/zine/discover-culture/calling-time-on-ie6">net magazine</a> is supporting a campaign to rid the world of IE6 – a browser that is still being used by a large proportion of people – asking the industry if the time has come for sites to no longer support IE6.</p>
<p class="MsoNormal">The magazine – a Future publication just like TechRadar – is hoping that Microsoft will port IE7 and IE8 to Windows 2000 allowing thousands of users to upgrade.</p>
<p class="MsoNormal"><strong>Shunned</strong></p>
<p class="MsoNormal">&#8220;Clearly, IE7 can&#8217;t be shunned: not supporting the current version of Microsoft&#8217;s market-leading browser would be a crazy move. However, with its predecessor now approaching its eighth birthday – positively ancient in software terms – should designers now ignore it until it fades away?&#8221; asks .<em>net</em>.</p>
<p class="MsoNormal">&#8220;That&#8217;s a really attractive thought,&#8221; Kleber&#8217;s Tom Muller answers, &#8220;but when a fifth or more of the audience still uses IE6, we can&#8217;t just drop it.&#8221;</p>
</blockquote>
<blockquote>
<p class="MsoNormal">It&#8217;s a valid point, and will be repeated by web designers the world over if they considered dropping support for the notorious IE6, but .<em>net</em>&#8216;s editor Dan Oliver insists that the time has come for the plug to be pulled.</p>
</blockquote>
<p><a href="http://www.techradar.com/news/software/applications/developers-issue-death-warrant-for-ie6-539017">Developers issue death warrant for IE6 | News | TechRadar UK</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.xploiter.com/c-and-aspnet/developers-issue-death-warrant-for-ie6-news-techradar-uk/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
