I've been playing around with IE 11, Firefox and Chrome. I've noticed while using FF and having Bing set as home starting page that the theme of the day, the ice berg and flowing river, that the flowing river doesn't move like it does in IE and Chrome with same set up. Anybody else seeing this.
📎 AI Summary:
The user initially noticed that the animated river on Bing’s homepage appeared static in Firefox but animated in IE 11 and Chrome. A responder suggested that the animation depends on a video file, which plays correctly in Firefox when accessed directly, implying browser support differences might be involved. Later, the original poster confirmed that the animation was working in Firefox after further checking, expressing confusion at the inconsistency. The overall tone is casual and a bit puzzled about browser rendering differences.
The user initially noticed that the animated river on Bing’s homepage appeared static in Firefox but animated in IE 11 and Chrome. A responder suggested that the animation depends on a video file, which plays correctly in Firefox when accessed directly, implying browser support differences might be involved. Later, the original poster confirmed that the animation was working in Firefox after further checking, expressing confusion at the inconsistency. The overall tone is casual and a bit puzzled about browser rendering differences.
Member details
- Joined
- Aug 3, 2010
- Messages
- 1,283
Not sure but it appears the file that's responsible for the animation is:
http://www.bing.com/az/hprichv/IcelandIceberg_GettyRR_157855754_EN-US.ogv
It would seem it plays ok when accessed directly in FF, so most likely there's a css element used or something similar which FF has not yet implemented.
Wouldn't be the first time pages render differently in different browsers due to features not being supported.
http://www.bing.com/az/hprichv/IcelandIceberg_GettyRR_157855754_EN-US.ogv
It would seem it plays ok when accessed directly in FF, so most likely there's a css element used or something similar which FF has not yet implemented.
Wouldn't be the first time pages render differently in different browsers due to features not being supported.