Эта тема была архивирована. Если вам нужна помощь, задайте новый вопрос.
Printed page date (foot note) incorrect.
Date: 10 May 2022 AusEST
Firefox 100.0 (64-bit) Mac desktop: Apple Silicon Mac mini (M1, 2020) - macOS Monterey v12.3.1 (problem occurred prior years using Intel/iMac 2015; and previous macOS) Extensions: DuckDuckGo Privacy Essentials; HTTPS Everywhere; NoScript Plugins: OpenH264 Video Codec provided by Cisco Systems,Inc. Location: Australia EST
I am wondering if the following is a known problem. If so, I haven’t been able to find the solution online.
I keep copies of home rental online payments as proof of payment should there be a discrepancy with the real estate agency.
This problem can also apply in other situations, for example payment of online purchases, or movement of large amounts of money to varying institutions.
Sometimes the bank payment is delayed and I would like to ensure that not only the date of payment is accurate but also that the time of payment is relatively close. I am finding that the file printed when banking via Firefox is not time dated relatively close to the time of payment. I use Firefox solely for banking as a secure method.
Upon payment I am presented with a bank receipt and an option to print it, all within Firefox’s desktop application. After pressing the PRINT button I choose to print as PDF and save to the computer. The resulting file is what I am referring to.
The pdf receipt is shown with default details at the top and bottom of the page, the bottom being where the date and time of pdf printing occurred. The discrepancy is between that time shown and the actual time of payment. The difference can be sometimes up to 12 hours!
Can someone please assist me to rectify the situation?
Kind regards, Harauld
Все ответы (11)
FredMcD has kindly responded with:
FredMcD Top 10 Contributor
Today at 2:27 PM
The pdf receipt is shown with default details at the top and bottom of the page . . .
The top and bottom details are called the header and footer. This is created by the software doing the printing. The time/date of the transaction should be in the main body of the message.
Hi, thanks for that (FredMcD). Not all receipts include the time of transaction within the body of the message unfortunately. That is why I am relying on the time stipulated in the footer which I have been expecting to be reasonably accurate.
I'm not sure to understand you well ... the date and time on the pdf are errornous - or these produced by your browser? (In the latter case, but I don't think it's so, your own systems date/time maybe errornous.)
A pdf file is usually printed by ff without a ff header and footer but with the header and footer the pdf contains. These are generated by the bank, I assume. The date and time are there local date and time. When you are living in the US there might by a reasonble difference to your local time. To make it more complicated, a lot of computers web apps don't use local time but GMT which might cause more difference. Or the server may be located on Hawaiian Islands, in Australia... and use their time?
All of this is unknown territory to me. Thank you for your input. It has helped to give me some insight.
Perhaps this issue is associated with the software that came with the printer I am using, or the printer software within the macOS operating system that is communicating with the printer.
Anyway, it's seeming more complicated than is desirable. It would have been nice to streamline the pdf printing process in the way I have originally discussed.
I notice that during the pdf print stage of saving the file to the computer I am given a choice of having a header and footer, and not. I think I will go with not having the header and footer and thus no time will be included at the bottom of the page. If a time reference is necessary, and the institution doesn't supply one in the receipt (pdf body) then reference can be made to the file's own data that can be found by searching 'file information'.
Kind regards, Harauld
I have just noticed that pdf printing (printing to file) within Firefox creates this discrepancy in the footer, however printing to file using Safari doesn't! It is appearing to be a Firefox issue, (I only trust Firefox for banking, for security).
Hi Dropa, thank you for your reply.
I always allow all cookies, and at end of each essential internet session I delete all History etc.. Nevertheless, within Firefox the only option I can see that may affect cookies is 'Enhanced Tracking Protection'. I tried turning that off however the 'Print to File' issue ensues.
I also tried disconnecting the 'Duckduckgo' extension, and the issue continues to ensue :)
Extensions in use: Duckduckgo Privacy Essentials HTTPS Everywhere NoScript
Even with these extensions disabled. They're the only ones in use.
In Private Mode when I perform the above disablements I still get the same results - thanks Dropa.
Am I the only one experiencing this? Is there anyone else experiencing this?
This is true. I had initially prepared an example image to present here but found that the image wouldn't upload. My first enquiry was regarding the failure of uploading an image, to which some people from within the Mozilla forum kindly responded with ways of presenting the image elsewhere, perhaps leaving a link within this conversation to an external location. It was starting to sound complicated. The file I was trying to upload was less than 500 KB. I tried png & jpg. However I have just reduced it's size to 143 KB (jpg) and will now try to attach it to this conversation.
No, it just keeps uploading without success :-(
I still have a feeling that the issue may be related to the printing software associated with either macOS (operating system) or with the software associated with the printer I use. The printer is turned off. I suppose I could try uninstalling the printer software but hesitate due to that being a tedious process to get right.
I have found that the situation can be replicated by printing to file any web page on Firefox. Anyone else able to replicate the issue?
Regarding the printer software - this still doesn't explain why the isue is within Firefox and not Safari web browser.