This may be related to the fact that Chrome has a built-in Flash plug-in, whereas the other browsers rely on Adobe's standard plug-in. Have you tried disabling this built-in Flash? If not, enter about:plugins into the address bar, find Flash in the list, and hit Disable. Restart the browser and check your website to see if the behavior has changed.

Calling it inferior or flawed because of a simple flash bug is a great exaggeration. All browsers have bugs.

This may be related to the fact that Chrome has a built-in Flash plug-in, whereas the other browsers rely on Adobe's standard plug-in. Have you tried disabling this built-in Flash? If not, enter about:plugins into the address bar, find Flash in the list, and hit Disable. Restart the browser and check your website to see if the behavior has changed.

That's just not realistic to expect users who visit the site to do that if they are using Chrome. The other browsers handle it fine, Chrome doesn't which is why I called it flawed.

It's got a bug that needs to be addressed.

Chrome's built in Flash plugin is the Adobe version (Shockwave), it's just packaged with Chrome instead of users needed to download and install it separately. The "flaw" could very well be in the Flash module, so don't be so quick to assume it's Chrome's fault.

it plays the intro once and then chokes and wont follow the actionscript to go to the end of the file and play the last frame.

What is the technical equivalent of "it chokes"? Can you be more specific? Does it play the entire video as if there was no cookie set, or does it do something bad like throw up an error message? Is there any way to add in some debug type of logging to your Flash application to see if it's a matter of it not finding the cookie, or something else?

It's playing the flash file one time through on the first visit like it should. But, when returning, instead of jumping from frame one, to the end where it should, it just stops at frame one so half the flash file is blank and it does not show any errors.

The flash actionscrip works perfect in every browser except chrome.

I'm not really going to pursue it because I don't have time to try and debug Googles program for them.

For now, users of Chrome who visit the site will get what they get.

That's just not realistic to expect users who visit the site to do that if they are using Chrome.

I never suggested that. It might simply be helpful to you in getting to the core of the problem.

If you don't want to bother to try and fix the problem, then why go to trouble of posting about it here? Now I feel as though this thread is just a waste of time.

I've narrowed it down to Chrome can't execute the action script like other browsers.

I thought maybe it was having a problem with the flash cookies. Removing the browser cookies doesn't remove a flash cookie so I opened the flash player manager and removed all flash cookies thinking maybe for some reason it was reading a cached version of an earlier flawed cookie.

Relaunching Chrome it opens the page fine and plays through the first time just fine, but if you move around the site, the header is not executing the action script to go to the last frame, it just stops at the first frame where the action script is placed. So, it's reading the cookie because it knows it's been there already but can't read the action script that says

} else {
gotoAndStop(119);
}

I posted here just in case a Googler happens to read it they know there is an issue with reading action script.

And there's always the "Report an Issue" option in the "Tools" menu of Chrome. :-)

>And there's always the "Report an Issue" option in the "Tools" menu of Chrome. :-)

I tried to use Chrome for a short time until I found one "interesting bug". Chrome loads pages from cache. It does not check if the page has been changed. It does not even allow to set the browser to check for updated pages. After a search in Google's own forums I found that the problem was known from ver. 4. And I had ver.10 on my computer at the time of discovery. So much for reporting. :)

As much as I would like to give Google benefit of doubt, this "bug" doesn't pass smell test. Google is trying by any means to make Chrome appear the fastest browser on the market. JMHO

Hi

having problems when loading my website in chrome browser
seems that the links don't load or work and exit pages won't load, Any suggestions as to why it won't work..a bug issue maybe..sorry newbie here

Thanks

In fairness, Chrome has one terrific feature that other browsers should hurry to swipe. The whole "history" package-- cache, cookies, everything-- can be lumped together and selectively erased for a time period you choose. This is obviously invaluable if you don't want your spouse, boss or roommate to know what you've been doing on the computer while they were gone.

You don't have to use Chrome yourself. But other people do, so you gotta allow for its quirks. And stop complaining. My e-texts have to work in MSIE 6 because They Who Rule refuse to upgrade.

Any suggestions as to why it won't work

My first guess is that there's an error on the page and the browser's that "work" have an error recovery routine that gets around it, but Chrome doesn't. Have you validated the mark-up?

W3C Validator - HTML [validator.w3.org]
W3C Validator - CSS [jigsaw.w3.org]