Hi Elena:
I'm experiencing the anomaly using Firefox 14.0.1 (FF).
I'm still not certain that Nick, Mohammad Reza
and I are experiencing the same problem. If not, I apologize to Nick for highjacking his thread.
Experimenting further with FF it appears that when it's caching 360cities URLs that it ignores parameters after the "#" character. Once it registers a URL with some ending, like #70.00,0.00,110.0 (for example) it uses this URL whenever any viewing parameters different than that are entered - including default ones coming from 360cities.
That's my face-value observation... what's really going on I'm not sure. Whatever is going on is something new I believe because I've never seen this behavior before. Don't know if it's due to a recent change in FF or 360cities.
I think what is happening is that while setting the initial view of a new pano that FF is caching a FOV other than the default. Then when the user views the newly published pano the first time they get a FOV different than the set default, because an alternate FOV URL was cached earlier. This makes it look like 360cities isn't capturing the desired FOV correctly.
I did find that clearing the FF cache clears up the problem.
What I was unable to determine (so far) is how FF decides which URL it will cache. I'm guessing this might have something to do with why this is showing up as an anomaly now.
I played around with Internet Explorer (9.0.7) a little and it doesn't appear to act the same as FF in this regard.
Calvin