Not signed in (Sign In)

Vanilla 1.0.3 is a product of Lussumo. More Information: Documentation, Community Support.

Safari 3.0 Beta on windows.

Bottom of Page

1 to 17 of 17

  1.  
    • CommentAuthorkarl
    • CommentTimeJun 11th 2007 edited
     
    There seems to be some issues here. The flash won't show up. Is there anyone else who has experience this problem yet?
    I can say its working on Safari on OSX, Firefox on OSX, IE Windows XP and FireFox Windows XP.
    • CommentAuthorkarl
    • CommentTimeJun 11th 2007
     
    Seems to be the.
    /* hide from ie on mac \*/
    html {
    height: 100%;
    overflow: hidden;
    }

    #flashcontent {
    height: 100%;
    }
    /* end hide */

    That caused it.
    • CommentAuthorGeoff
    • CommentTimeJun 12th 2007
     
    that's odd... it doesn't break on a mac. i wonder if there's a new css selector bug in the windows build..
    • CommentAuthorGeoff
    • CommentTimeJun 12th 2007 edited
     
    So I grabbed the beta 3 for osx, and tested my fullpage.html page here:

    http://blog.deconcept.com/swfobject/fullpage.html

    and it works fine. Can anyone verify that that page breaks in safari beta 3 on windows?
    • CommentAuthorphilip
    • CommentTimeJun 12th 2007
     
    the test page loads fine for me
    (Safari 3 beta, WinXP Pro)

    - philip
    • CommentAuthorthacker
    • CommentTimeJul 13th 2007
     
    Have been testing the swfoject within a local asp.net environment and it does break in Safari 3 Beta for Windows.

    Why, I have no idea.
    • CommentAuthorphilip
    • CommentTimeJul 13th 2007
     
    that's a pretty general statement... does it break on a bare-bones asp page containing nothing but the swfobject code? is there other javascript present that could be causing a conflict?

    can you provide a code example or link to a non-functioning page?
    • CommentAuthorthacker
    • CommentTimeJul 13th 2007 edited
     
    philip--

    Here is a link to an asp.net content page that uses the SWFObject and fails within Safari for Windows v3.02 BETA.

    http://boinkinchipmunks.com/web/flash/smily/safari.aspx

    The SWFObject fails in no other major browser, including the ability to use the express install method within the JavaScript.

    Anything else needed, please ask.

    Thank you very much.

    Addendum--

    I am not so sure that this particular rendering issue within Safari is, yet, worth the time to evaluate. Safari for Windows is still a BETA. For all I know this issue may reside within the Beta version and not within the SWFObject script.
    • CommentAuthorphilip
    • CommentTimeJul 13th 2007 edited
     
    i can confirm that your page isn't working in Safari. however, all of Geoff's examples work in Safari (including the express install example).

    you have 4 different javascript files included on your page. 2 are SWFObject-related and 2 are not. since SWFObject works fine in Safari when the other JS files aren't present, my guess is that your issue might be due to Safari's handling of these other scripts.

    i created a barebones HTML file that has no content except your SWF, and SWFObject created a SWF instance properly in Safari.

    code:

    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
    <title>SWFObject example: Safari</title>

    <script type="text/javascript" src="/scripts/swfobject.js"></script>

    </head>

    <body>

    <div id="flashcontent"></div>

    <script type="text/javascript">
    // <![CDATA[
    var so = new SWFObject("http://boinkinchipmunks.com/App_Themes/Flash/Smily/smilylg.swf",
    "smily", "500", "400", "9.0.47.0", "#333333");
    so.useExpressInstall('http://boinkinchipmunks.com/App_Themes/Flash/Smily/expressinstall.swf');
    so.addParam("base", "http://boinkinchipmunks.com/App_Themes/Flash/Smily/Smily/");
    so.addParam("allowScriptAccess", "sameDomain");
    so.addParam("swliveconnect", "true");
    so.write("flashcontent");
    // ]]>
    </script>
    </body>
    </html>


    - philip
    • CommentAuthorthacker
    • CommentTimeJul 13th 2007
     
    philip--

    Thank you very much.

    The only other JavaScript used within that content are the Microsoft commissioned CSS Friendly Control Adapters.

    Should I kick this issue to the Safari engineers? Should I kick this issue to Microsoft?

    Microsoft, yeah, right. They are always itching to handle bugs particularly bugs that affect their apps and Apple.

    Again, thanks.
    • CommentAuthorphilip
    • CommentTimeJul 13th 2007
     
    before kicking it up to anyone, i'd confirm that you're actually encountering a bug. strip the page down to its bare elements (no css or javascript aside from SWFObject, use minimal markup/page content), then test it. if SWFObject works, restore the elements you removed one by one, testing each edit in Safari. it's a slow process, but will usually show you where the problem lies.

    if you are able to determine the cause of the problem -- assuming it's a bug, which it might not be -- you're more likely to know who to contact, and will be able to give them useful troubleshooting and debugging information.

    note also that my test file wasn't asp, it was a standard xhtml file using XHTML 1.0 (transitional). your file is XHTML 1.1, which is much stricter than 1.0. you might want to try different doctypes when you troubleshoot... personally, i'd stick to XHTML 1.0 (strict or transitional)... XHTML 1.1 is generally frowned upon. O'Reilly's HTML and XHTML: The Definitive Guide says this:

    In our opinion, XHTML 1.1 is an example of the standards process taken to absurd levels, defining a standard that may be academically pure but is essentially unusable.


    - philip
    • CommentAuthorthacker
    • CommentTimeJul 13th 2007
     
    philip--

    Thanks, again. My fallback position is that the content page as coded renders correctly, except for the CSS within IE wherein I have purposely not provided design correction for any IE browser, in all major browsers except for Safari for Windows.

    I will follow your advice and strip out elements, script, css while keeping the asp.net format and get a closer handle on where the problem is actually occuring. I will drop back the DTD with each change. This has to be done to validate the problem is not within the structure or code that I have created and is, actually, someone else's problem. If the issue is found to reside within a JavaScript conflict, I will leave it at that and not get into tearing apart and analyzing someone else's work product.

    As far as XHTML 1.1, I am in a very small minority but on a continued mission that development of "academically pure" functional content that includes a very high accessibility level is a good thing.

    For the hell of it and for anyone else's benefit, I will post results here.

    Again, Philip, thank you very much for your time and your advise. It is appreciated.
    • CommentAuthorphilip
    • CommentTimeJul 13th 2007
     
    no problem, i hope you figure it out, and that it turns out to be something simple and easy to fix! :)

    regarding doctypes, there's a huge debate raging over HTML 5 versus XHTML 2 versus XHTML 1.1 versus XHTML 1.0... it's getting pretty ugly, and -- for us developers who WANT to follow a standard -- extremely confusing and disheartening. when the standardistas have such sharp divisions and can't even agree on what specification to stick with, you know it's gonna be a rough ride.

    good luck
    - philip
    •  
      CommentAuthorw2look
    • CommentTimeJul 13th 2007 edited
     
    I am running windows xp and I can't get any of my flash embedded with swfobject to work in Safari 3.0 beta. Does anyone have any suggestions?

    Everything works fine in both IE7 and Firefox 2.0.0.4

    For an example, you can view this test header and try it in all 3 browsers.
    • CommentAuthorphilip
    • CommentTimeJul 13th 2007
     
    w2look:

    the swfobject.js link (<script type="text/javascript" src="http://www.where2lookonline.com/flash/swfobject.js"></script>) should be in the document <head>, not in <body>.

    please follow Geoff's example:
    http://blog.deconcept.com/swfobject/swfobject.html

    it's also a good idea to keep your <script> tags out of divs.

    - philip
    •  
      CommentAuthorw2look
    • CommentTimeJul 16th 2007
     
    thanks, I'll try that.
    • CommentAuthorzhangsisi
    • CommentTimeOct 1st 2007
     
    the find best www.ConnectAsia.info/en/lang104082about_sisi11 welcome you

1 to 17 of 17

  1.