<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:schema="http://schema.org/" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" version="2.0" xml:base="https://www.snakehill.net/taxonomy/term/11">
  <channel>
    <title>Browsers</title>
    <link>https://www.snakehill.net/taxonomy/term/11</link>
    <description/>
    <language>en</language>
    
    <item>
  <title>Big browser changes for Firefox and Chrome</title>
  <link>https://www.snakehill.net/blog/big-browser-changes-firefox-and-chrome</link>
  <description>&lt;div data-history-node-id="33" class="node node--type-blog-post node--view-mode-rss ds-1col clearfix"&gt;

  

  &lt;div class="field-wrapper field field-node--field-media field-name-field-media field-type-entity-reference field-label-hidden"&gt;
    &lt;div class="field-items"&gt;
          &lt;div class="field-item"&gt;  &lt;img src="https://www.snakehill.net/sites/default/files/styles/image_above_full_content/public/2018-01/Chrome%20and%20Firefox_4.jpg?itok=8Y9LfWbX" width="389" height="223" alt="Thumbnail" typeof="foaf:Image" /&gt;&lt;/div&gt;
      &lt;/div&gt;
&lt;/div&gt;
&lt;div class="field-wrapper field field-node--node-title field-name-node-title field-type-ds field-label-hidden"&gt;
    &lt;div class="field-items"&gt;
          &lt;div class="field-item"&gt;&lt;h1&gt;
  Big browser changes for Firefox and Chrome
&lt;/h1&gt;
&lt;/div&gt;
      &lt;/div&gt;
&lt;/div&gt;
&lt;div class="field-wrapper field field-node--dynamic-token-fieldnode-clean-submitted-by field-name-dynamic-token-fieldnode-clean-submitted-by field-type-ds field-label-hidden"&gt;
    &lt;div class="field-items"&gt;
          &lt;div class="field-item"&gt;&lt;p&gt;By Daniel Schiavone on December 13, 2017&lt;/p&gt;
&lt;/div&gt;
      &lt;/div&gt;
&lt;/div&gt;
&lt;div class="field-wrapper body field field-node--body field-name-body field-type-text-with-summary field-label-hidden"&gt;
    &lt;div class="field-items"&gt;
          &lt;div class="field-item"&gt;&lt;p&gt;There have been some big changes in Firefox and Chrome browsers recently. In November, &lt;a href="https://www.mozilla.org/en-US/firefox/new/"&gt;Firefox&lt;/a&gt; released a completely revamped browser called &lt;em&gt;&lt;strong&gt;Quantum&lt;/strong&gt;&lt;/em&gt;. The new Firefox is significantly faster and has a new cutting edge user interface. These days it's hard to make a splash with a browser release but Firefox Quantum will make you want to switch your desktop browser. There are also many compelling reasons for moving to an Open Source. The most important is privacy. Considering the amount of data being collected by the &lt;a href="https://www.nytimes.com/2017/05/10/technology/techs-frightful-five-theyve-got-us.html"&gt;Frightful Five&lt;/a&gt;, the benefits of moving to &lt;a href="https://www.mozilla.org/en-US/firefox/new/"&gt;Firefox&lt;/a&gt; have become more compelling.   &lt;/p&gt;

&lt;p&gt;Meanwhile, Google has been pushing out a new version of Chrome. What a contrast in releases. Google has been warning users that the new release will label all pages not using SSL (HTTPS) as 'Not secure'. But the change goes much deeper. If your network connection isn't configured properly you might get a nasty message.&lt;/p&gt;
&lt;img alt="Error message" data-entity-type="file" data-entity-uuid="4383dec8-3aeb-4088-935c-14d5ee4dd3cb" src="https://www.snakehill.net/sites/default/files/inline-images/secure%20connection.jpg" class="align-center" /&gt;&lt;p&gt; &lt;/p&gt;

&lt;p&gt;Help desks are going to be busy over the holidays. &lt;a href="https://productforums.google.com/forum/#!topic/chrome/u6LHQ35_Cug"&gt;Here are some ways to troubleshoot&lt;/a&gt; if you get this message. &lt;/p&gt;

&lt;p&gt;The update also introduces a redirect for any domain with a ".dev" extension to HTTPS. A lot of web developers are going to be searching Google to find why their local development site displays in other browsers but not Chrome. Developers might know about the new warnings about insecure sites but I suspect many of us missed the nuances of Chrome's latest release.&lt;/p&gt;
&lt;/div&gt;
      &lt;/div&gt;
&lt;/div&gt;
&lt;div class="field-wrapper field field-node--field-tags field-name-field-tags field-type-entity-reference field-label-hidden"&gt;
    &lt;div class="field-items"&gt;
          &lt;div class="field-item"&gt;&lt;a href="https://www.snakehill.net/taxonomy/term/11" hreflang="en"&gt;Browsers&lt;/a&gt;&lt;/div&gt;
      &lt;/div&gt;
&lt;/div&gt;


&lt;/div&gt;

</description>
  <pubDate>Wed, 13 Dec 2017 18:06:50 +0000</pubDate>
    <dc:creator>Daniel Schiavone</dc:creator>
    <guid isPermaLink="false">33 at https://www.snakehill.net</guid>
    </item>

  </channel>
</rss>
