Tags: https

1233

sparkline

Monday, January 27th, 2020

Checked in at Faculty Of Arts. Here for a Design Council event. map

Checked in at Faculty Of Arts. Here for a Design Council event.

Wednesday, January 22nd, 2020

Checked in at Jolly Brewer. Session — with Jessica map

Checked in at Jolly Brewer. Session — with Jessica

Saturday, January 11th, 2020

Checked in at Fourth & Church. Aperitif — with Jessica map

Checked in at Fourth & Church. Aperitif — with Jessica

Thursday, January 9th, 2020

Checked in at Jolly Brewer. Wednesday night session 🎶 — with Jessica map

Checked in at Jolly Brewer. Wednesday night session 🎶 — with Jessica

Monday, January 6th, 2020

Browser defaults

I’ve been thinking about some of the default behaviours that are built into web browsers.

First off, there’s the decision that a browser makes if you enter a web address without a protocol. Let’s say you type in example.com without specifying whether you’re looking for http://example.com or https://example.com.

Browsers default to HTTP rather than HTTPS. Given that HTTP is older than HTTPS that makes sense. But given that there’s been such a push for TLS on the web, and the huge increase in sites served over HTTPS, I wonder if it’s time to reconsider that default?

Most websites that are served over HTTPS have an automatic redirect from HTTP to HTTPS (enforced with HSTS). There’s an ever so slight performance hit from that, at least for the very first visit. If, when no protocol is specified, browsers were to attempt to reach the HTTPS port first, we’d get a little bit of a speed improvement.

But would that break any existing behaviour? I don’t know. I guess there would be a bit of a performance hit in the other direction. That is, the browser would try HTTPS first, and when that doesn’t exist, go for HTTP. Sites served only over HTTP would suffer that little bit of lag.

Whatever the default behaviour, some sites are going to pay that performance penalty. Right now it’s being paid by sites that are served over HTTPS.

Here’s another browser default that Rob mentioned recently: the viewport meta tag:

I thought I might be able to get away with omitting meta name="viewport". Apparently not! Maybe someday.

This all goes back to the default behaviour of Mobile Safari when the iPhone was first released. Most sites wouldn’t display correctly if one pixel were treated as one pixel. That’s because most sites were built with the assumption that they would be viewed on monitors rather than phones. Only weirdos like me were building sites without that assumption.

So the default behaviour in Mobile Safari is assume a page width of 1024 pixels, and then shrink that down to fit on the screen …unless the developer over-rides that behaviour with a viewport meta tag. That default behaviour was adopted by other mobile browsers. I think it’s a universal default.

But the web has changed since the iPhone was released in 2007. Responsive design has swept the web. What would happen if mobile browsers were to assume width=device-width?

The viewport meta element always felt like a (proprietary) band-aid rather than a long-term solution—for one thing, it’s the kind of presentational information that belongs in CSS rather than HTML. It would be nice if we could bid it farewell.

Sunday, January 5th, 2020

Checked in at The Prince Albert. A few more bands and then it’s time for Salter Cane map

Checked in at The Prince Albert. A few more bands and then it’s time for Salter Cane

Wednesday, January 1st, 2020

Checked in at Jolly Brewer. First session of the year — with Jessica map

Checked in at Jolly Brewer. First session of the year — with Jessica

Sunday, December 29th, 2019

Checked in at The Bugle Inn. Session 🎻 — with Jessica map

Checked in at The Bugle Inn. Session 🎻 — with Jessica

Checked in at Fox On the Downs. Sunday roast — with Jessica map

Checked in at Fox On the Downs. Sunday roast — with Jessica

Wednesday, December 18th, 2019

Checked in at Jolly Brewer. A packed house for the session! 🎶 — with Jessica map

Checked in at Jolly Brewer. A packed house for the session! 🎶 — with Jessica

Saturday, December 14th, 2019

Picture 1 Picture 2
map

Checked in at Fletcher Cove

Friday, December 13th, 2019

I feel seen.

I feel seen.

Thursday, December 12th, 2019

Checked in at Internet Archive map

Checked in at Internet Archive

Checked in at Ritual Coffee Roasters map

Checked in at Ritual Coffee Roasters

Checked in at Taqueria El Farolito map

Checked in at Taqueria El Farolito

Picture 1 Picture 2
map

Checked in at La Taqueria

Checked in at Blue Bottle Coffee map

Checked in at Blue Bottle Coffee

Wednesday, December 11th, 2019

Checked in at Plough & Stars. 🎶 map

Checked in at Plough & Stars. 🎶

Tuesday, December 10th, 2019

Checked in at The Westin St. Francis on Union Square map

Checked in at The Westin St. Francis on Union Square

Monday, December 9th, 2019

Checked in at Plough & Stars. Sunday night session 🎻🎵 map

Checked in at Plough & Stars. Sunday night session 🎻🎵