- From: L. David Baron <dbaron@dbaron.org>
- Date: Sat, 9 Apr 2016 23:40:11 -0700
- To: Philippe Wittenbergh <ph.wittenbergh@l-c-n.com>
- Cc: www-style list <www-style@w3.org>
- Message-ID: <20160410064011.GA17011@pescadero.dbaron.org>
On Sunday 2016-04-10 15:27 +0900, Philippe Wittenbergh wrote: > Sample URL: https://www.w3.org/TR/css3-sizing/ and https://www.w3.org/TR/css3-selectors/ > Browser: Safari 9.1 and 9.x TP > > console flags: > [Warning] [blocked] The page at https://www.w3.org/TR/css3-sizing/ was not allowed to run insecure content from http://www.w3.org/StyleSheets/TR/W3C-WD.css. (css3-sizing, line 12) > > [Warning] The page at https://www.w3.org/TR/css3-sizing/ was allowed to display insecure content from http://www.w3.org/Icons/w3c_home. (css3-sizing, line 17) > > A quick look at the source of the page reveals that the stylesheet is linked with an absolute (non-https) URL > http://www.w3.org/StyleSheets/TR/W3C-WD.css > > Firefox otoh is apparently less strict and loads the stylesheet. I havenβt checked what others do. The issue is not being less strict, but rather supporting https://www.w3.org/TR/upgrade-insecure-requests/ which is able to auto-convert that link to https *before* the mixed content check happens. The best public discussion of this issue that I've been able to find is the set of slides, in French, at: https://www.w3.org/Talks/2016/0402-jdll-lyon-jk/ particularly slide 9: https://www.w3.org/Talks/2016/0402-jdll-lyon-jk/#(9) www-style probably isn't the best forum for the discussion, though. Maybe https://lists.w3.org/Archives/Public/spec-prod/ ?? It is certainly a known issue; I've heard it discussed in in-person conversations. -David -- π L. David Baron http://dbaron.org/ π π’ Mozilla https://www.mozilla.org/ π Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914)
Received on Sunday, 10 April 2016 06:40:37 UTC