Bug 157472 - [GTK] Blogger editor is invisible
Summary: [GTK] Blogger editor is invisible
Status: RESOLVED DUPLICATE of bug 156935
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: Other
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-09 04:53 PDT by Bastien Nocera
Modified: 2016-06-02 05:43 PDT (History)
5 users (show)

See Also:


Attachments
blogger.png (53.88 KB, image/png)
2016-05-09 04:53 PDT, Bastien Nocera
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bastien Nocera 2016-05-09 04:53:06 PDT
Created attachment 278402 [details]
blogger.png

webkitgtk4-devel-2.12.2-2.fc24

With the following errors:
Refused to load the script 'https://www.blogger.com/static/v1/gwt/deferredjs/C7B4B081968986544D7D8B6925D71A83/13.cache.js' because it violates the following Content Security Policy directive: "script-src 'self' *.google.com *.google-analytics.com 'unsafe-inline'   'unsafe-eval' *.gstatic.com *.googlesyndication.com *.blogger.com   *.googleapis.com uds.googleusercontent.com https://s.ytimg.com   www-onepick-opensocial.googleusercontent.com   www-bloggervideo-opensocial.googleusercontent.com   www-blogger-opensocial.googleusercontent.com https://www.blogblog.com".
Comment 1 Michael Catanzaro 2016-05-09 06:06:52 PDT
So you think the bug is that *.blogger.com is listed in the CSP, but the resource is being refused anyway? I don't know much anything about CSP.
Comment 2 Brent Fulgham 2016-05-27 12:14:35 PDT
This is not happening on OS X. Whatever the issue is might be in code that is unique to SOUP or GTK.
Comment 3 Michael Catanzaro 2016-05-31 13:05:49 PDT
(In reply to comment #2)
> This is not happening on OS X. Whatever the issue is might be in code that
> is unique to SOUP or GTK.

Well it's of course possible, but certainly not the most likely solution... could it have been fixed in trunk after we branched? Dan, any chance this looks familiar?
Comment 4 Daniel Bates 2016-06-01 23:52:52 PDT
(In reply to comment #3)
> (In reply to comment #2)
> > This is not happening on OS X. Whatever the issue is might be in code that
> > is unique to SOUP or GTK.
> 
> Well it's of course possible, but certainly not the most likely solution...
> could it have been fixed in trunk after we branched? Dan, any chance this
> looks familiar?

Closing this bug as a duplicate of bug #156935. I suspect webkitgtk4-devel-2.12.2-2.fc24 does not contain <http://trac.webkit.org/changeset/200030>. If this is not the case and this issue still reproduces then please re-open this bug with the revision of WebKit used, reproduction steps and the full URL of the blogger.com page that this issue was observed on and any Web Inspector console messages that were emitted. If you can also provide the CSP policy of the page (if it differs from the policy mentioned in comment #0) that would be helpful. The CSP policy of the page may either be delivered via an HTTP header or via an HTML meta element. The former can be seen in the Resource side bar when the affected page is selected in the Resource view of the Web Inspector. The latter can be seen in the markup of the page.

*** This bug has been marked as a duplicate of bug 156935 ***
Comment 5 Michael Catanzaro 2016-06-02 05:38:40 PDT
(In reply to comment #4)
> Closing this bug as a duplicate of bug #156935. I suspect
> webkitgtk4-devel-2.12.2-2.fc24 does not contain
> <http://trac.webkit.org/changeset/200030>.

Correct. That commit was backported for 2.12.3, so Bastien please let us know if it's fixed in 2.12.3.
Comment 6 Bastien Nocera 2016-06-02 05:43:07 PDT
(In reply to comment #5)
> (In reply to comment #4)
> > Closing this bug as a duplicate of bug #156935. I suspect
> > webkitgtk4-devel-2.12.2-2.fc24 does not contain
> > <http://trac.webkit.org/changeset/200030>.
> 
> Correct. That commit was backported for 2.12.3, so Bastien please let us
> know if it's fixed in 2.12.3.

Yep, that fixed it, thanks.