This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24628 - spec has (almost) no style (or scripts)
Summary: spec has (almost) no style (or scripts)
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - HTML Editing APIs (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Ms2ger
QA Contact: HTML Editing APIs spec bugbot
URL: https://dvcs.w3.org/hg/editing/raw-fi...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-12 04:34 UTC by Samuel Bronson
Modified: 2014-02-16 14:06 UTC (History)
4 users (show)

See Also:


Attachments

Description Samuel Bronson 2014-02-12 04:34:15 UTC
I'm using "Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Firefox/24.0 ID:20140131092626 CSet: d06a17a96fa2" (actually version 24.3.0), and when I try to view the spec (from the link on <https://developer.mozilla.org/en-US/docs/Web/API/Selection>), I get a very understyled page.

The problem becomes (reasonably) clear if we look at "Developer Tools: Web Console":

[21:56:19.480] GET https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html#selections [HTTP/1.1 200 Script output follows 641ms]
[21:56:19.878] Blocked loading mixed active content "http://www.whatwg.org/style/specification" @ https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html#selections
[21:56:20.381] Blocked loading mixed active content "http://www.whatwg.org/specs/web-apps/current-work/dfn.js" @ https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html#selections
[... skipped irrelevant deprecation warning caused by some extension ...]
[21:56:23.642] GET http://www.w3.org/Icons/w3c_home [HTTP/1.1 200 OK 16ms]
[21:56:23.653] The Web Console logging API (console.log, console.info, console.warn, console.error) has been disabled by a script on this page.

(Actually, this pasted text is clearer than what was on the screen ...)

So, it seems Firefox decided that it's had enough of people trying to use "http://" resources from an "https://" document and finally put its foot down.

Unfortunately, the obvious workaround (delete the "s") does not work because that redirects back to the https:// address :-(.
Comment 1 Aryeh Gregor 2014-02-16 12:24:07 UTC
Aha -- it seems that whatwg.org has acquired SSL support since I last checked.  Should be easy to fix, then.  If anyone with W3C hg access wants to make the necessary changes, please feel free.  My hg is not working properly at the moment.  You'll want to change both source.html and editing.html (no need to rebuild it).  Maybe Ms2ger or Anne?  Should take two minutes.

I'll put it on my list of stuff to deal with in case no one else gets to it, as well.
Comment 2 Ms2ger 2014-02-16 14:06:15 UTC
Forgot this was filed as a bug too. I fixed this earlier:

https://dvcs.w3.org/hg/editing/rev/28f516366550