Bug 519667 - ctrl+w, close on file menu, close button on tab don't work.
ctrl+w, close on file menu, close button on tab don't work.
Status: RESOLVED INVALID
Product: epiphany
Classification: Core
Component: General
2.21.x
Other All
: Normal normal
: gnome-2-22
Assigned To: Epiphany Maintainers
Epiphany Maintainers
:
: 521369 (view as bug list)
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2008-03-01 03:00 UTC by sangu
Modified: 2008-04-06 21:09 UTC (History)
2 users (show)

See Also:
GNOME target: ---
GNOME version: 2.21/2.22

Attachments
implement new nsIFilePicker interface (775 bytes, patch)
2008-03-13 16:46 UTC, Alexander Sack 		none Details | Diff | Review
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Description sangu 2008-03-01 03:00:32 UTC 
Please describe the problem:
ctrl+w, close on file menu, close button on tab don't work.

Steps to reproduce:
1. lanunch epiphany
2.  ctrl + n
3.  ctrl + w


Actual results:


Expected results:


Does this happen every time?
yes, always.

Other information:
OS Fedora development (rawhide 20080229)
xulrunner-1.9-0.beta3.30.nightly20080228.fc9.i386.
Comment 1 Cosimo Cecchi 2008-03-09 18:54:24 UTC 
*** Bug 521369 has been marked as a duplicate of this bug. ***
Comment 2 Alexander Sack 2008-03-13 16:46:37 UTC 
Created attachment 107230 [details] [review]
implement new nsIFilePicker interface

simply fixing the build - by applying this patch - fixes it for me.
Comment 3 Christian Persch 2008-03-13 17:20:07 UTC 
You need to #ifdef that, since 1.8 branch has the old version of this interface. Or maybe we just declare --enable-filepicker unsupported on 1.8 ?
Comment 4 sangu 2008-03-14 07:10:23 UTC 
Fixed in epiphany-2.22.0-1.fc9.i386 and xulrunner-1.9-0.40.cvs20080312.fc9.i386.
Maybe xulrunner bug?
Comment 5 Cosimo Cecchi 2008-03-14 10:38:30 UTC 
Reopening, as we have a patch here (maybe Fedora ships that) and we took no decisions about what we should do.
Comment 6 Christian Persch 2008-04-06 21:09:05 UTC 
The patch was committed (it has nothing to do with this bug).

The bug isn't reproducible anymore, closing.
Note You need to log in before you can comment on or make changes to this bug.