W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2014

[Bug 24628] New: spec has (almost) no style (or scripts)

From: <bugzilla@jessica.w3.org>
Date: Wed, 12 Feb 2014 04:34:15 +0000
To: public-webapps@w3.org
Message-ID: <bug-24628-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24628

            Bug ID: 24628
           Summary: spec has (almost) no style (or scripts)
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
               URL: https://dvcs.w3.org/hg/editing/raw-file/tip/editing.ht
                    ml
                OS: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML Editing APIs
          Assignee: ayg@aryeh.name
          Reporter: naesten@gmail.com
        QA Contact: sideshowbarker+html-editing-api@gmail.com
                CC: mike@w3.org, public-webapps@w3.org

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 :-(.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 12 February 2014 04:34:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:21 UTC