Savings documents is a big part of using a browser, whether it be
receipts, or information to access later, etc. it is one of the most
common uses of any browser. So then, why does Firefox save a document
by creating a separate folder and html page? This requires a user to
rename the folder and place the html page inside of the folder. This
is way to many steps for saving a web page. Safari (and others) use a
singular archive file, allowing me to simply name the file (should it
need another name, often the default is sufficient) then choose where
I want to file it. Very simple. Firefox’s system is inefficient in
comparison, as it requires additional steps and movement of the html
page into the renamed folder full of the web page components, which
makes even finding the correct html page difficult when it's retrieval
is needed. This alone is the only reason I don’t use the browser as
my default browser! I would imagine others who don’t use it for the
same reason.
Change this and many users, including myself, will use Firefox as the
default browser, as Safari does a poor job staying up to the current
web standards. I occasionally have to launch Firefox to properly read
a page or be able to access a process link button, such as when making
airline reservations and the button is not visible in Safari. In this
situation, Firefox is superior to Safari. BUT, for all the archiving I
do, I will never use Firefox as my main browser until they change
this inefficient method of archiving.
Maybe I'm missing something, but I've been unable to save and archive
without dealing with two files; the page component folder and the html
page itself. One needing the other for retrieval.
Mac power user