<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Browser on Matt Allford</title><link>https://www.mattallford.com/tags/browser/</link><description>Recent content in Browser on Matt Allford</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Thu, 07 Jan 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://www.mattallford.com/tags/browser/index.xml" rel="self" type="application/rss+xml"/><item><title>Brave Browser: Azure Portal - Something Went Wrong</title><link>https://www.mattallford.com/2021/Brave-Browser-Azure-Portal-Something-Went-Wrong/</link><pubDate>Thu, 07 Jan 2021 00:00:00 +0000</pubDate><guid>https://www.mattallford.com/2021/Brave-Browser-Azure-Portal-Something-Went-Wrong/</guid><description>TL;DR - In the last few days (start of 2021), the &amp;ldquo;Shields Up&amp;rdquo; feature in the Brave web browser seems to be flagging a JSON file as a cross-site tracker when creating a resource in Azure, causing the blade to not load. To work around this, you can go &amp;ldquo;shields down&amp;rdquo; for portal.azure.com.
I logged on to my machine yesterday, same as any other day, and went to start deploying some resources to Azure via the Azure Portal for a customer, nothing out of the ordinary.</description></item></channel></rss>