firefox opens files read-only
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
firefox (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
firefox-3.0 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: firefox
this bug relates to #90378 but since that is marked as fix-released i open a new one.
please let me know if this is not the correct way of doing this.
Firefox3 Hardy Heron.
firstly i actually consider this new behavior as a bug as it does not solve what it intended to do in the first place.
second i' m not sure if its desirable to want this in the first place.
if you don' t save your file, you loose it. that is something i can explain to someone and makes sense, besides firefox opens it from a read only place (the internet) so you can always retrieve the original.
i can understand that the "SAVE" button should not be available and only the "SAVE AS" or should default to a "SAVE WHERE" dialog when in /tmp but this workaround simply doesn' t cut it in my opinion.
i find this highly annoying and disruptive behavior, i have 70 users depending on firefox and a web application that makes contracts, invoices, custom documents etc.... opening in openoffice.org
1 they don' t understand why their document is read-only all of a sudden
2 using the "edit" button gives two confusing messages that look like error messages
3 after they used the "edit" button and went through the two errors, the file itself is still not saved anywhere else the /mp
4 the web application gives files an understandable name, e.g contract-
I' m pretty confident that i am not the only one who sees it this way so i ope this gets fixed in Hardy but i might be wrong off course so i will try to find a way to let firefox3 return to its default behavior or use firefox2 instead.
> if you don' t save your file, you loose it. that is something i can explain
> to someone and makes sense, > besides firefox opens it from a read only
> place (the internet) so you can always retrieve the original.
The point is that even if you save the file, you loose it. With the current behaviour,
you at least notice that something is wrong. Hence I don't think that reverting to the
old behaviour is an option. As you say yourself, the internet is read-only, hence it
is only natural that the file is also read-only when you edit it.
Concerning you web application, your description makes it very difficult to
understand what the problem actually is, but it sounds more like a bug is
the web application.