Closed
Bug 1230787
Opened 9 years ago
Closed 7 years ago
Remember the "save image" window position
Categories
(Core :: XUL, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: condacum, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.0; rv:42.0) Gecko/20100101 Firefox/42.0 Build ID: 20151029151421 Steps to reproduce: Save image http://postimg.org/image/55gmojwfn/ from the main window: ok Actual results: Save image http://postimg.org/image/55gmojwfn/ if I Save from a new window, this "Save image window" moves itself on the top left corner. Save imga efrom the main window, after the previous task, again in the top left corner. Expected results: If I move the window at the center of the browser, because I prefer so, FF should mantain the position of the Save image window even after using this feature in a NEW window, without changing the desired position.
Updated•9 years ago
|
Summary: save image window position → Remember the "save image" window position
Comment hidden (obsolete) |
Comment 2•9 years ago
|
||
please avoid previous comment which was mistakenly done, but targeted for another bug. marked that comment as obsolete. this looks like something belonging to XUL
Component: Untriaged → XUL
Product: Firefox → Core
Updated•9 years ago
|
QA Whiteboard: [testday-20151207] → [bugday-20151207]
did you notice this behaviour too? its strange that after using Save Image in a new window, then the position of the save-image-window (on the main window, bottom) doesnt remain fixed at the center of the page, as wished.
Comment hidden (spam) |
Comment hidden (spam) |
Comment hidden (spam) |
Comment hidden (spam) |
Comment hidden (spam) |
Comment 9•7 years ago
|
||
Looks like broken "xulstore.json" file in your Firefox profile [1], so delete it (backup will be nice before it). If it not helps, it's Windows system issue. [1] = https://support.mozilla.org/t5/Install-and-Update/Profiles-Where-Firefox-stores-your-bookmarks-passwords-and-other/ta-p/4608
Has Regression Range: --- → no
Flags: needinfo?(condacum)
Reporter | ||
Comment 10•7 years ago
|
||
If it is a windows problem, why the issue happens in firefox only?
Flags: needinfo?(condacum)
Comment 11•7 years ago
|
||
Did you try tip mentioned in Comment #9? (In reply to Yorgos from comment #10) > If it is a windows problem, why the issue happens in firefox only? Ask Microsoft developers, why their file picker didn't save its window position on Firefox.
Flags: needinfo?(condacum)
Reporter | ||
Comment 12•7 years ago
|
||
yes. Have I to ask to Microsoft about an issue that arise in firefox only? Am I the only user with this issue?
Flags: needinfo?(condacum)
Reporter | ||
Comment 13•7 years ago
|
||
as usual "the other" are fault. a default reply.
Comment 14•7 years ago
|
||
(In reply to Yorgos from comment #12) > yes. > Have I to ask to Microsoft about an issue that arise in firefox only? Yes, but not expect fix, using obsolete and not supported Microsoft system, which is Windows Vista. (In reply to Yorgos from comment #12) > Am I the only user with this issue? Looking on Bugzilla reports, yes, you're the only one with this issue. (In reply to Yorgos from comment #13) > as usual "the other" are fault. > a default reply. It's Microsoft file picker issue, so blame them, that their file picker didn't save its window position on Firefox and it could be also in other software. Per this and https://blog.mozilla.org/futurereleases/2016/12/23/firefox-support-for-xp-and-vista/ , I'm marking this bug as INVALID.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 15•7 years ago
|
||
No, Vista is still supported! until april 2017 and I opened the bug one year ago!!! so, what did you in the time 2015-2017?? I blame Virtual_Man, the idler.
Comment 16•7 years ago
|
||
(In reply to Yorgos from comment #15) > No, Vista is still supported! > until april 2017 and I opened the bug one year ago!!! So no point even wasting Mozilla developers time for system which its support will end in one month. (In reply to Yorgos from comment #15) > so, what did you in the time 2015-2017?? > I blame Virtual_Man, the idler. Blame yourself for not reporting this issue to Microsoft and for not fixing it yourself, as Firefox is open source software, which you can openly contribute, as everyone here.
Reporter | ||
Comment 17•7 years ago
|
||
but where are you in the time 2015-2017, when the system was fully supported? tell me, what are you doing in bugzilla, other than closing bugs and causing waste of time to 10-years-users? (the life is a wheel: what you do for me, in the future somebody - in other fields of life too - will do the same for you, and perhaps you will be not so satisfied. at the moment I anathematize you).
Comment 18•7 years ago
|
||
(In reply to Yorgos from comment #17) > but where are you in the time 2015-2017, when the system was fully supported? > tell me, what are you doing in bugzilla, other than closing bugs and causing > waste of time to 10-years-users? > > (the life is a wheel: what you do for me, in the future somebody - in other > fields of life too - will do the same for you, and perhaps you will be not > so satisfied. at the moment I anathematize you). Blame yourself for not reporting this issue to Microsoft fast enough, so it will be fixed by them by this time, as it's not Firefox issue and Mozilla doesn't have anything to do with it. I'm ending this pointless discussion.
Group: core-security
Status: RESOLVED → VERIFIED
Has Regression Range: no → ---
QA Whiteboard: [bugday-20151207]
Updated•7 years ago
|
CC list accessible: false
Not accessible to reporter
Updated•7 years ago
|
Group: core-security
You need to log in
before you can comment on or make changes to this bug.
Description
•