Regarding screen shots, you may have better luck attaching them to a reply. If you have a newer "higher than HD" display, you might resize the window so the image isn't so wide.

When you get the day old results, does a reload bypassing the cache help? On Mac, I believe it's Command+Shift+r.

1. The reload didn't help. It actually took me back a couple of steps and when I moved back to the time frame I wanted, same results. 2. You were correct about the screen shots. I got further when I tried to attach them to this reply. However, they are too big and, when I reduced the window size, the screenshot file actually became larger because it picked up all the stuff on my descktop. I tried to reduce the resolution on the screen but don't see how to do that under the system preferences - screen.

I use Windows, but I think on Mac you can grab a screenshot of just the Firefox window. Check out this article: https://support.apple.com/en-us/HT201361

I'm puzzled by this problem. There are many ways the page might request data from a certain range, but a specific date range (unlike "today" or "yesterday") should never give the wrong result.

Did the site mention whether factors like the time zone set on your system could affect the chart?

OK, we are making progress and, I learned something new - Thanks. Attached are 2 screenshots, both done today (Saturday) so no market action to influence anything. On the left image notice the price in the upper left corner and the price at the top middle of the lower (6 month) chart are the same. On the right image (3 months) notice that not only are the prices different but the bars on the lower chart are one day short of the 6 month chart. Again, doesn't always happen and the site can't replicate it. I also learned that the back arrow on this window doesn't work 100% - I clicked on one of the images to check my facts and when I used the back arrow, all the text was missing.

Sorry about the back button, I know how painful that is because it happens to me, too. This page has instructions not to cache it so any time to go back it gets updated from the server.

I created a combined image showing the comparison (attached).

There are two possible issues here:

(1) A script in the browser is computing the start and end dates and sending them to the server, and there is a problem in the script. (2) The error is on the server side.

You could rule out #2 if Safari shows the correct date range. Do you know whether the site was testing on their end in Firefox or in other browsers?

I think diagnosing #1 would require a subscription to the site and more motivation than I have on a Saturday morning...

I appreciate your help. Your answer #1 is way above me so, I will try using Safari for a while and seen if the issue shows up there. If the problem doesn't show do you have any suggestions besides continuing to use Safari? They said they tested IE, FF, and Chrome and had no issues. Again, Thanks for your help and, I totally understand uses for a Saturday.