Where are the trailers?

When I click on a movie the url says it's Apple. http://trailers.apple.com/trailers/paramount/thor/

Which movies do you think are missing?

Nothing has been removed.

http://trailers.apple.com/

Click any of the movies then click View Trailer.

Having the same problem the past couple of days on my 27-inch iMac. Not sure when it started since I haven't checked Apple's movie page in a while. It's the same problem in Safari, Firefox and Camino. No problem on my four-year-old MBP or iPad. (All available updates applied to all machines.) I've repaired permissions, reset Safari, even rebooted, all to no avail.

Both Safari and Firefox report lots of CSS errors, and some Javascrpt errors:

Error: Builder is not defined

Source File: http://trailers.apple.com/trailers/global/scripts/lib/overlay_panel.js

Line: 66

Error: illegal character

Source File: http://trailers.apple.com/trailers/global/scripts/lib/scriptaculous.js

Line: 1

Source Code: �

In Firefox 4.x on my MBP, the trailers load fine. The CSS errors appear the same, but there's just one Javascript error, and it's a different one:

AC.Detector.svgAsBackground is not a function

Beats me. ;-)

I have the exact same problem on my 27" iMac, Safari 5.0.5. Not sure when it started - maybe a week ago. Everything else seems to work fine - Apple product videos, iTunes trailer videos, but no sign of trailers even existing on http://trailers.apple.com/ ( including nowhere to click view trailer ).

Same with Firefox 4.0.1

Nope. Still no trailers area.

It's really curious - the rectangle which contains the trailers in your image of the X-Men page is completely missing. Not an empty box which looks like something should have been there but a continuation of the background texture as if the page were built without the trailer area to begin with.

Having the same problem. Using an IBM Lenovo X61 Thinkpad running Windows XP. It behaves the same in IE8, Firefox, Safari, and Google Chrome. Firebug (Firefox plugin) shows the first part of the "scriptaculous.js" javascript file as unreadable characters:

In my case, this is the root cause of the missing drop-down.

"scriptaculous.js" doesn't appear this way on my MacBook Pro, Vista pcs, or Win7 pcs....the code reads normal. It must be something to do with the OS & its ability to interpret whatever character set the first portion (894 lines) of "scriptaculous.js" has been saved in.

Seeing the same results on that scriptaculous.js file.

So - bear with me, I'm not particularly tech savvy - this section of the web page where scriptaculous ( that's just a Freeway feature isn't it? ) is used, is all of a sudden causing problems?

I don't think it's the file on Apple's end. I think it's something to do with the "state of the OS" (in this case, his 27-in. IMac running [whatever], and my Lenovo running WinXP). I have several XP machines here at work, all running IE7, and they can see the trailer drop-down just fine....it has to be something that I installed/changed on my Lenovo that is causing the corruption.

Scriptaculous is a web 2.0 Javascript library. It comes pre-packaged in many web development frameworks (Ruby on Rails, Seaside, etc), but is also available for general download & use:

http://script.aculo.us/

Apple is using it, or maybe even a modified version of it, in trailers.com.

But, like I mentioned before...I don't think it's the file itself...if it was, the problem would be much more wide-spread. Rather, I think it's my computer's mode & method of interpreting said file that's causing the issue. It HAS to be something I installed or changed....the questions is, what.

robertfromsherwood wrote:

But, like I mentioned before...I don't think it's the file itself...if it was, the problem would be much more wide-spread. Rather, I think it's my computer's mode & method of interpreting said file that's causing the issue. It HAS to be something I installed or changed....the questions is, what.

Agreed, it's specific to our systems, and not the browsers, since the problem persists through three browsers on my iMac. Yet it's apparently easily enough to trigger, either through installation, update or some other method; while's it's not common, it's also not an isolated incident.

Thankfully, it's not a huge problem, but one of those nagging technical faults I'd love to solve.

Agreed, more of a puzzle than a problem. I'll slowly begin to deinstall, install, deactivate, activate and try to narrow it down. Hopefully someone will discover the sequence or program which is the culprit.