WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED INVALID
53956
[GTK] When opening new windows WebKitGTK+ does not properly pass statusbar, locationbar and toolbar properties to the client
https://bugs.webkit.org/show_bug.cgi?id=53956
Summary
[GTK] When opening new windows WebKitGTK+ does not properly pass statusbar, l...
Martin Robinson
Reported
2011-02-07 16:13:26 PST
This can be seen through the failure of fast/dom/Window/new-window-opener.html. Test diff: --- /tmp/layout-test-results/fast/dom/Window/new-window-opener-expected.txt 2011-02-07 16:12:35.622434003 -0800 +++ /tmp/layout-test-results/fast/dom/Window/new-window-opener-actual.txt 2011-02-07 16:12:35.622434003 -0800 @@ -12,15 +12,15 @@ PASS newWin.scrollbars.visible is false Toolbar -FAIL newWin.toolbar.visible should be true. Was false. +PASS newWin.toolbar.visible is true PASS newWin.toolbar.visible is false -FAIL newWin.toolbar.visible should be true. Was false. +PASS newWin.toolbar.visible is true PASS newWin.toolbar.visible is false Statusbar -FAIL newWin.statusbar.visible should be true. Was false. +PASS newWin.statusbar.visible is true PASS newWin.statusbar.visible is false -FAIL newWin.statusbar.visible should be true. Was false. +PASS newWin.statusbar.visible is true PASS newWin.statusbar.visible is false Menubar @@ -30,9 +30,9 @@ PASS newWin.menubar.visible is isMenubarAlwaysExpected Locationbar -FAIL newWin.locationbar.visible should be true. Was false. +PASS newWin.locationbar.visible is true PASS newWin.locationbar.visible is false -FAIL newWin.locationbar.visible should be true. Was false. +PASS newWin.locationbar.visible is true PASS newWin.locationbar.visible is false PASS window.successfullyParsed is true
Attachments
Add attachment
proposed patch, testcase, etc.
Carlos Garcia Campos
Comment 1
2011-03-03 04:33:06 PST
Looking at the test code and results, I don't see what's wrong here. The test says On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". and that's exactly what we have, but the expected file have several FAIL. I've noticed that chromium-win has its own expected file, so maybe we should just add our own.
Martin Robinson
Comment 2
2011-03-03 08:29:26 PST
Hrm. I think you're right about this one! I'll unskip the test and close this bug. Thanks.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug