The article goes on to say that "The decision does not affect already existing standards/features, but Mozilla hopes all Firefox features "will be considered on a case-by-case basis," and will slowly move to secure contexts (HTTPS) exclusively in the future." That doesn't sound like you'll be blocked from visiting non-HTTPS sites for routine browsing.

Some more on it from Mozilla Edict - the RegisterSeems it's relative to footprint, exposed services and new development needing to be more secure.Closing off http would be a pretty substantial move and with some systems using http for other programs possibly problematic.

DanRaisch wrote:The article goes on to say that "The decision does not affect already existing standards/features, but Mozilla hopes all Firefox features "will be considered on a case-by-case basis," and will slowly move to secure contexts (HTTPS) exclusively in the future." That doesn't sound like you'll be blocked from visiting non-HTTPS sites for routine browsing.

Yes as Dan said, you should be able to access this site, just fine. Again, I imagine Mozilla wants to keep making things safer for all users.