[Webkit-unassigned] [Bug 153697] New: [GTK] Some new CSP tests are failing with one-space difference in output

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jan 29 21:00:05 PST 2016


https://bugs.webkit.org/show_bug.cgi?id=153697

            Bug ID: 153697
           Summary: [GTK] Some new CSP tests are failing with one-space
                    difference in output
    Classification: Unclassified
           Product: WebKit
           Version: Other
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Gtk
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: mcatanzaro at igalia.com
                CC: bugs-noreply at webkitgtk.org

The following layout tests have been failing for GTK since they were added in r195367:

http/tests/security/contentSecurityPolicy/object-src-applet-archive-codebase.html [ Failure ]
http/tests/security/contentSecurityPolicy/object-src-applet-archive.html [ Failure ]
http/tests/security/contentSecurityPolicy/object-src-applet-code-codebase.html [ Failure ]
http/tests/security/contentSecurityPolicy/object-src-applet-code.html [ Failure ]

The only difference from the expected output is that there is one extra space character that doesn't exist on the other ports:

-This test passes if there is a console message saying the plugin was blocked. The test must be run manually; ContentShell doesn't support applet in DumpRenderTree mode. :(
+This test passes if there is a console message saying the plugin was blocked. The test must be run manually; ContentShell doesn't support applet in DumpRenderTree mode. :( 

(Select those lines to note the whitespace difference at the end of the lines.)

I'm tempted to just add expected results with the space, but I have no clue where the space is coming from; it doesn't seem right. So I will instead mark these as failing for now.

Also, I'm not pleased that (a) this is a manual test outside of the ManualTests directory, and (b) there is no console message saying that the plugin was blocked even when running the test manually (at least in 2.10.4; maybe that was one of the recent fixes?).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160130/36137f12/attachment-0001.html>


More information about the webkit-unassigned mailing list