Closed Bug 752800 Opened 12 years ago Closed 11 years ago

Menu items do not work at http://theamazingspiderman.com/ mobile site

Categories

(Web Compatibility :: Site Reports, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jjensen, Unassigned)

References

()

Details

(Whiteboard: [Engagement][contactready][country-all] [serversniff])

My son found this one:

Web page or screen you were on when you saw the issue: 

http://www.theamazingspiderman.com/mobile/#

Steps to reproduce:
1. Go to http://www.theamazingspiderman.com/ and rotate phone to landscape mode
2. Click "menu" button at top right
3. List of options comes up for Videos, Story, Characters, Cast, Game, etc
4. No matter which one you select, nothing happens; works fine in Google Chrome Beta

What you expected: 

To be able to click on menu items and have them work

Crash report ID (if applicable):
OS: Mac OS X → Android
Hardware: x86 → ARM
The page uses event.srcElement which is not supported in Gecko as far as I can tell. This page doesn't work on desktop Firefox either, and the error console shows the relevant JS error. Moving to evangelism but also marking dependent on bug 453968 which is a bug to add support for event.srcElement.
Component: General → Evangelism
Depends on: 453968
QA Contact: general → evangelism
Component: Evangelism → Mobile
Product: Firefox for Android → Tech Evangelism
Version: Trunk → unspecified
Another issue with this site is the backgrounds of the image carousel are too big:

line 251 of main.css
#promo-carousel li a.sweeps {
    background: url("../images/carousel-getaway-2x.png") no-repeat scroll 0px 0px transparent;
}

has higher specificity than 

#promo-carousel li a {
  background-size: 100%;
}

So background-size of auto auto is applied.

They need to change that to background: url("../images/carousel-getaway-2x.png") no-repeat scroll 0px 0px / 100% transparent; in #promo-carousel li a.sweeps.

The same CSS bug is apparent in Chrome... but not Safari for some reason.

So someone needs to contact them about not using srcElement and tweaking the background-size of the carousel images.
Whiteboard: [Engagement] → [Engagement][contactready][country-all]
So there is server side sniffing obviously. But the site is broken I'm not sure if there's hope to get things fixed. In addition usually these microsites are made as a promo site by a Web Agency and are never touched again (been there, done that). They are like flyers to be thrown.

On Firefox for Android, after loading the main site, I have a menu to swype up, when I say access the official site, I get a black screen. nothing. When rotating I get the initial screen and all the issues already explained in other comments


I'm willing to close it as WONTFIX.



	<script type="text/javascript">
		
		cdn("cdn/"); 
		userBrowser("Firefox"); 
		deviceType("mobile");
		browserVersion("mobile"); 
		siteUrl("http://www.TheAmazingSpiderman.com");      
		browserType("mobile");
		userAgent("Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0"); 
		modernBrowser("true"); 
		viewPort("width=720"); 
		trace("1")
		        
		//alert("Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0")
		//trace("cdn = "+cdn()+" userBrowser = "+userBrowser()+" deviceType = "+deviceType()+" browserVersion = "+browserVersion()+" siteUrl = "+siteUrl()+" browserType = "+browserType()+" viewPort = "+viewPort());

	</script>
Whiteboard: [Engagement][contactready][country-all] → [Engagement][contactready][country-all] [serversniff]
I'd imagine there's nearly nobody people visiting the Amazing Spiderman site after the movie came out over a year ago.
Searching a bit more here and there, who could have done the Web site. I found 5 agencies in different countries for different parts of the brands and products. :) To just try to fix will be time sinking. :)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Product: Tech Evangelism → Web Compatibility
Component: Mobile → Site Reports
You need to log in before you can comment on or make changes to this bug.