Best way to learn web design, business web design, graphic web design, web design development, web design services
Monday, November 9, 2009
W3C compliance with Macromedia Flash
W3C compliance with Macromedia Flash A creative solution to validate pages with Macromedia Flash and XHTML specifications prevent Microsoft Inteet Explorer. Remember the "Good Housekeeping Seal?" W3C is the World Wide Web Consortium stamp of quality assurance for your website, provide guidelines to ensure your website and will function properly regardless of browser, resolution, or the device used. In other words, ensure that the site is clean of bugs and problems and can be properly displayed on all search engines. Everyone needs a well functioning website that performs well in the SERP (the results pages of search engines) to business practices. According to experts in SEO Beanstock, many examples of best sites after they were brought into compliance with W3C standards After reading the aforementioned article, I decided to do some 'light cleaning and our site came time to dust and off the cobwebs to bring compliance with the W3C standards to improve performance SERP. Value Cross Media specializes in creating web and online advertising, search engine marketing and Flash Video presentations for the web in a SERP benefits is a top priority for our business. To my great surprise, it was easier said than done. I could not validate the site for now. 'HAH! I thought. "I have 15 + years of experience in design, only 10 online, then you should be able to do so. After all, it's just cleaning marks, change the attributes, right? 'It is at the table and a couple of hours doing research on Google. I finally came to an article entitled "Flash satay: Embedding Macromedia Flash While standards support. "In Macromedia.com Flash satay of" author Drew McLellan, in an article originally published in the "List A" writes, "embed" is not part of the XHTML specification and prevent page validation. It is used by Netscape and similar browsers for displaying Flash movies. The parameters are passed in the name / value attribute pairs. McLellan goes on to say, "Netscape created the" embed "on how to integrate plug-ins and players in web pages. The "code" tag is not part of the XHTML specification, and although some browsers other than Netscape do not support that, is not compatible with the rules, so you should not use. " 'OK, I thought,' then there are some obstacles, but we are approaching the solution. Our website contains a Macromedia Flash movie embedded. The solution is to clean up the brand and change some attributes. "In a follow-up to the flash satay McLellan article also says:" Flash has built in safeguards that make life really difficult. If the Flash player thinks the movie is loaded from a different domain than your page is built, which gives and does nothing. It also seems that it is very easy to confuse the Flash Player in thinking that this is the case. Flasher, beware! "Hours later, after cleaning and changing the scope of my thinking attributes page was finally ready to be validated for compliance with W3C. I thought it worked well in Netscape and Mozilla, but when I tried in Inteet Explorer (IE) was stopped dead in its tracks. It 'been a measure of security in Flash Player has stopped the movie, or Inteet Explorer to create their own rules? Suddenly, memories of Netscape vs IE in the first 90, when it began as a web designer, said in my mind. CSS remember what it was visible only in Inteet Explorer, then? I decided that as long as the browser, Macromedia and Microsoft, I decided to play together better to find a creative solution to get the job done. I dusted off an old browser detection and redirection scripts in NetMechanic.com just detects the browser and redirects to the page. The script is useful when you change to redirect users to a page optimized for the browser. Even if you should spend time optimizing your individual pages to different browsers, the script is very simple. Finally, I created two pages, one optimized for IE, which is validated with the W3C CSS seal and a second page is optimized for browsers such as Netscape, Mozilla, etc. to be validated for the specific XHTML their support. Java script detects the browser and redirects to the appropriate page. To see an example of this, I try to open the Mozilla browser and then try IE. You can see the difference in the label below the Flash movie, but the pages remain the same. The best part is that they are compatible with the W3C. If you have any comments, suggestions or creative solutions of their own in reference to this article, please send us a note or visit our blog We will be pleased to hear from you. If you want to know how Valor Cross Media can help you call 212 288-1866 or write to galina@valorcrossmedia.com
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment