<?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>chrome - SAJE</title>
	<atom:link href="https://saje.nz/tag/chrome/feed/" rel="self" type="application/rss+xml" />
	<link>https://saje.nz</link>
	<description>Web Gardners</description>
	<lastBuildDate>Sat, 07 Oct 2017 04:26:46 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://saje.nz/wp-content/uploads/2023/05/cropped-logov1-32x32.png</url>
	<title>chrome - SAJE</title>
	<link>https://saje.nz</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>The Inevitable Move to Secure Web Pages</title>
		<link>https://saje.nz/2017/10/07/the-inevitable-move-to-secure-web-pages/</link>
					<comments>https://saje.nz/2017/10/07/the-inevitable-move-to-secure-web-pages/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sat, 07 Oct 2017 04:26:46 +0000</pubDate>
				<category><![CDATA[NZ Industry News]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[certificate]]></category>
		<category><![CDATA[chrome]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[not secure]]></category>
		<category><![CDATA[ssl]]></category>
		<guid isPermaLink="false">https://braveweb.nz/rebuild22/index.php/2017/10/07/the-inevitable-move-to-secure-web-pages/</guid>

					<description><![CDATA[<p>As with most things on the internet related to Google, what Google wants, they usually get. In this instance we are talking about a secure web. It sounds like a good idea and now Google is taking steps to encourage everyone to move in that direction. From earlier this year, the Google Chrome browser would [&#8230;]</p>
<p>The post <a href="https://saje.nz/2017/10/07/the-inevitable-move-to-secure-web-pages/">The Inevitable Move to Secure Web Pages</a> first appeared on <a href="https://saje.nz">SAJE</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>As with most things on the internet related to Google, what Google wants, they usually get.</p>
<p>In this instance we are talking about a secure web.</p>
<p>It sounds like a good idea and now Google is taking steps to encourage everyone to move in that direction.</p>
<p><img class=\"alignright size-full wp-image-1409\" src=\"http://deepweb.co.nz/wp-content/uploads/2017/10/notsecure.jpg\" alt=\"\" width=\"144\" height=\"50\" />From earlier this year, the Google Chrome browser <a href=\"https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html\" target=\"_blank\" rel=\"noopener\">would identify all pages like login forms</a> and other pages requiring passwords and credit card numbers were flagged as \&#8221;Not Secure\&#8221;</p>
<p>This was done as a gentle nudge to website owners that Google would like all pages on the internet to be secure. (Secure in this context means that the pages are protected by SSL or Secure Sockets Layer, and information passed between your computer and the website is encrypted so that anyone snooping on your communications couldn\&#8217;t read it)</p>
<p>To further this objective, it is reported that in October all pages with forms in them (and if you include a signup form on every page, then all pages will be flagged) will be marked as not secure if the page is not secured using a SSL certificate.</p>
<p>The end goal is that all website across the internet will be secure and any without SSL certificates will be highlighted as being insecure.</p>
<p>From a trust perspective it is important to make sure you move to SSL relatively quickly</p>
<p>To this end we will be ensuring all of our clients\&#8217; websites are protected by SSL and we are going through this process at the moment.</p>
<p>If your site is not SSL protected, you need to talk to your host or webs designer about getting it done.</p><p>The post <a href="https://saje.nz/2017/10/07/the-inevitable-move-to-secure-web-pages/">The Inevitable Move to Secure Web Pages</a> first appeared on <a href="https://saje.nz">SAJE</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://saje.nz/2017/10/07/the-inevitable-move-to-secure-web-pages/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Firefox is an Abomination &#8211; Unfortunately</title>
		<link>https://saje.nz/2010/08/25/firefox-is-an-abomination-unfortunately/</link>
					<comments>https://saje.nz/2010/08/25/firefox-is-an-abomination-unfortunately/#comments</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Wed, 25 Aug 2010 06:20:57 +0000</pubDate>
				<category><![CDATA[Soapbox]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[chrome]]></category>
		<category><![CDATA[firebug]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[footiefox]]></category>
		<category><![CDATA[ie]]></category>
		<category><![CDATA[scribefire]]></category>
		<guid isPermaLink="false">https://braveweb.nz/rebuild22/index.php/2010/08/25/firefox-is-an-abomination-unfortunately/</guid>

					<description><![CDATA[<p>Well I suppose it had to happen. It was all going so well, good memory management, it was fast and had great addons. It was a no brainer to use Firefox as my default browser. Version 3 was better than Version 2, this is how software evolution was supposed to be. And the only reason [&#8230;]</p>
<p>The post <a href="https://saje.nz/2010/08/25/firefox-is-an-abomination-unfortunately/">Firefox is an Abomination – Unfortunately</a> first appeared on <a href="https://saje.nz">SAJE</a>.</p>]]></description>
										<content:encoded><![CDATA[<p><strong>Well I suppose it had to happen.</strong></p>
<p>It was all going so well, good memory management, it was fast and had great addons. It was a no brainer to use Firefox as my default browser.</p>
<p>Version 3 was better than Version 2, this is how software evolution was supposed to be.</p>
<p>And the only reason I still had Internet Explorer on my machine was that I needed  it to test my websites.</p>
<p>Chrome was good and fast, but Firefox had all those great addons: <a href=\"http://en.footiefox.com/\" target=\"_blank\">FootieFox</a> for my Football scores, WHOIS tools, <a href=\"http://www.scribefire.com/\" target=\"_blank\">ScribeFire</a> for writing my blog posts and the best of the lot <a href=\"http://getfirebug.com/\" target=\"_blank\">FireBug</a>.</p>
<p>Alas, since 3.6.8 was released my Firefox utopia has been shattered.</p>
<p>It has gotten to the point that I have had to shift to Chrome. Had to, not wanted to.</p>
<p>The memory leaks were so bad, that after coming back from being away from my desk for half a day, Firefox was consuming over 1gb of memory, for only 4 tabs!</p>
<p>It got to the point where I was rebooting 3 times a day to maintain any speed.</p>
<p>Luckily, since I have moved to Chrome, my work experience is much better, the speed is back and I found that there was an extension for Chrome called Firebug Lite, I am Saved!</p>
<p>If Mozilla sort out the memory problems, I may go back. But the major problems need some serious tweaks.</p>
<p>Have you found your favourite Browser or other software made by non monoply (Microsoft, Adobe) etc has succumbed to bloat and decreasing performance?</p>
<p>Have they gotten lazy as market share has risen?</p><p>The post <a href="https://saje.nz/2010/08/25/firefox-is-an-abomination-unfortunately/">Firefox is an Abomination – Unfortunately</a> first appeared on <a href="https://saje.nz">SAJE</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://saje.nz/2010/08/25/firefox-is-an-abomination-unfortunately/feed/</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
			</item>
		<item>
		<title>IE6, What Do We Do About It?</title>
		<link>https://saje.nz/2009/12/02/ie6-what-do-we-do-about-it/</link>
					<comments>https://saje.nz/2009/12/02/ie6-what-do-we-do-about-it/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Wed, 02 Dec 2009 04:26:06 +0000</pubDate>
				<category><![CDATA[Coders Stuff]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[adobe]]></category>
		<category><![CDATA[browserlab]]></category>
		<category><![CDATA[chrome]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[ie6]]></category>
		<category><![CDATA[ie7]]></category>
		<category><![CDATA[ie8]]></category>
		<category><![CDATA[kalena]]></category>
		<category><![CDATA[opera]]></category>
		<category><![CDATA[osx]]></category>
		<category><![CDATA[safari]]></category>
		<guid isPermaLink="false">https://braveweb.nz/rebuild22/index.php/2009/12/02/ie6-what-do-we-do-about-it/</guid>

					<description><![CDATA[<p>Kick it to the Kerb? That would be nice, as most web designers have come unstuck when a nice design fails spectacularly in IE6. But unfortunately, there are still lots of people (over 30% in most cases) that are still using it, that is too large a number to upset with messages about compatibility and [&#8230;]</p>
<p>The post <a href="https://saje.nz/2009/12/02/ie6-what-do-we-do-about-it/">IE6, What Do We Do About It?</a> first appeared on <a href="https://saje.nz">SAJE</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>Kick it to the Kerb?</p>
<p>That would be nice, as most web designers have come unstuck when a nice design fails spectacularly in IE6.</p>
<p>But unfortunately, there are still lots of people (over 30% in most cases) that are still using it, that is too large a number to upset with messages about compatibility and the like.</p>
<p>Some new designs from template makers will not work properly in Internet Explorer 6 and they provide warnings and encourage users to upgrade.</p>
<p>If you target corporate users, this is not a wise choice as some will still use IE6 across their organisation and IT are not keen to roll out IE7 or 8.</p>
<p>I have even recently visited a primary school that is still using IE6 in all of it\&#8217;s classrooms.</p>
<p>For designers, testing in multiple browser brands involves installing the different browsers and testing as you go, however, my suite of browsers include:</p>
<ul>
<li>IE8</li>
<li>Firefox 3</li>
<li>Firefox 2</li>
<li>Google Chrome</li>
<li>Opera 9</li>
<li>Opera 10</li>
</ul>
<p>Notice that some browsers allow multiple versions to be installed simultaneously. This is a great thing for testing.</p>
<p>However, you can only install one version of IE, (there is a hacked version that allows older ones as well, but that seems a bit scary)</p>
<p>Recently, I found out about <a target=\"_blank\" href=\"https://browserlab.adobe.com/index.html\">BrowserLab</a> from Adobe, (Thanks @kalena) it is a great tool that lets you test browsers online without having to install them on your machine.</p>
<p>You enter the address of the site you want to test and the browsers you want to test on, and let it do it\&#8217;s magic, you get presented with an image of what the result is for each browser.</p>
<p>Here is a list of all browsers:</p>
<ul>
<li>Firefox 2.0, 3.0 and 3.5 under XP</li>
<li>Internet Explorer 6.0, 7.0 and 8.0 under XP</li>
<li>Chrome 3.0 under XP</li>
<li>Safari 3.0 and 4.0 under OSX</li>
<li>Firefox 2.0, 3.0 and 3.5 under OSX</li>
</ul>
<p>Having Safari and Firefox under OSX is great too. No Opera yet, but I assume they will appear in time.</p>
<p>Good to see a useful resource hitting the web.</p>
<p>Do you have any web resources that you \&#8221;must have\&#8221;, let me know in the comments.</p>
<div class=\"zemanta-pixie\"><img class=\"zemanta-pixie-img\" alt=\"\" src=\"http://img.zemanta.com/pixy.gif?x-id=2f5dd35c-b8e5-8fcc-83a8-dee9dee001f0\" /></div><p>The post <a href="https://saje.nz/2009/12/02/ie6-what-do-we-do-about-it/">IE6, What Do We Do About It?</a> first appeared on <a href="https://saje.nz">SAJE</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://saje.nz/2009/12/02/ie6-what-do-we-do-about-it/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>HTML 5 &#8211; The future looks bright</title>
		<link>https://saje.nz/2009/07/21/html-5-the-future-looks-bright/</link>
					<comments>https://saje.nz/2009/07/21/html-5-the-future-looks-bright/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 21 Jul 2009 02:54:43 +0000</pubDate>
				<category><![CDATA[Coders Stuff]]></category>
		<category><![CDATA[Cool Stuff]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[chrome]]></category>
		<category><![CDATA[chromium]]></category>
		<category><![CDATA[html 5]]></category>
		<category><![CDATA[html5]]></category>
		<category><![CDATA[safari]]></category>
		<guid isPermaLink="false">https://braveweb.nz/rebuild22/index.php/2009/07/21/html-5-the-future-looks-bright/</guid>

					<description><![CDATA[<p>HTML 4 has been around for many years, and it looks like the newest incarnation HTML5 is going to make some serious changes to the way the web works. Here is a video for those who are interested (it is over an hour long, and targetted at a technical audience, but very informative) Here are [&#8230;]</p>
<p>The post <a href="https://saje.nz/2009/07/21/html-5-the-future-looks-bright/">HTML 5 – The future looks bright</a> first appeared on <a href="https://saje.nz">SAJE</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>HTML 4 has been around for many years, and it looks like the newest incarnation HTML5 is going to make some serious changes to the way the web works.</p>
<p>Here is a video for those who are interested (it is over an hour long, and targetted at a technical audience, but very informative)</p>
<div class=\"youtube-video\"><object width=\"425\" height=\"344\"><param name=\"movie\" value=\"http://www.youtube.com/v/AusOPz8Ww80&amp;color1=0xb1b1b1&amp;color2=0xcfcfcf&amp;hl=en&amp;feature=player_embedded&amp;fs=1\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowScriptAccess\" value=\"always\"></param><embed src=\"http://www.youtube.com/v/AusOPz8Ww80&amp;color1=0xb1b1b1&amp;color2=0xcfcfcf&amp;hl=en&amp;feature=player_embedded&amp;fs=1\" type=\"application/x-shockwave-flash\" allowfullscreen=\"true\" allowscriptaccess=\"always\" width=\"425\" height=\"344\"></embed></object></div>
<p>Here are some Highlights:</p>
<ul>
<li>Offline Storage including offline database storage</li>
<li>Adding video will be as simple as adding an image to a webpage</li>
<li>Forms will be much simpler, yet complete (things like calendars for dates etc)</li>
<li>Geolocation API\&#8217;s so you can get the location of a mobile device via the browser</li>
<li>Drag and Drop</li>
<li>Better interaction with the Operating System</li>
<li>Canvas, being able to generate images dynamically</li>
</ul>
<p>So there are plenty of cool things coming. Alreadt Google Chrome, Safari and a few other browsers (including iphone and android mobile devices) are already handling HTML5. However, there are not many websites that are written in HTML5 to take advantage of this.</p>
<p>Older versions of Internet Explorer (version 6 and older) won\&#8217;t work as it is too old and one fight will be getting people to upgrade their browser so they can access these new features</p>
<p>We may be building dual websites for a while!</p>
<div class=\"zemanta-pixie\"><img class=\"zemanta-pixie-img\" src=\"http://img.zemanta.com/pixy.gif?x-id=2bb20d9a-9058-8afc-ad8e-a3828bc14894\" /></div><p>The post <a href="https://saje.nz/2009/07/21/html-5-the-future-looks-bright/">HTML 5 – The future looks bright</a> first appeared on <a href="https://saje.nz">SAJE</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://saje.nz/2009/07/21/html-5-the-future-looks-bright/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
