Not signed in (Sign In)

SkillShare - A place to discuss Web Standards and Web Design topics

Categories

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

    •  
      CommentAuthorahicox
    • CommentTimeSep 5th 2006
     permalink
    Hello everyone:

    I'm trying to use XHTML 1.0 Transitional for a page that also contains a google map.
    Everything works fine in all browsers, as long as the Content-type is (incorrectly) set to text/html.

    When I change the response header to (correctly) specify 'application/xhtml+xml' for the Content-type, my google map completely dissapears, but only in Firefox. Safari, and I.E. seem to roll with it just fine.

    Has anyone seen this before? Know a fix?
    I'd prefer to send the correct Content-type.
    • CommentAuthorPettyRider
    • CommentTimeSep 5th 2006 edited
     permalink
    application/xhtml+xml throws all sorts of DOM errors. It's a standard, but maybe not a practical one yet. I'd say just step off the high-horse for a little bit and be practical about these things for now.
    •  
      CommentAuthornifkin
    • CommentTimeSep 5th 2006 edited
     permalink
    1- use the off content type (you'll need to for ie/pc anyway).

    2- embed external files using <object > tags (that don't work quite right in ie/pc either) to pull in HTML 4 pages just containing your map code, etc.

    <object data="/src/ad-468.html" type="text/html" class="ad468"></object>

    FWIW: my site is xhtml1.1 sent as application/xhtml+xml and i'd say there's no real viable reason to bother doing it. The hacks and modifications you need to wedge into place to get it to work just don't make the "geek street cred payoff" worthwhile.
    •  
      CommentAuthornifkin
    • CommentTimeSep 5th 2006 edited
     permalink
    application/xhtml+xml throws all sorts of DOM errors.

    application/xhtml+xml is peachy for any DOM stuff I've ever seen. The problem in most cases is that document.write(); isn't supported with that content type, you're forced to use DOM instead.
  1.  permalink
    "application/xhtml+xml is peachy for any DOM stuff I've ever seen"

    Maybe I'm just regurgitating rumors, then, as I've never run across any myself. :)
    •  
      CommentAuthorahicox
    • CommentTimeSep 6th 2006
     permalink

    Thanks for the tips guys ('specially importing html files with <object> ... that's feindishly clever, my friend)
    In any case, yeah I guess I'll have to go with sending text/html for now.



    The main reason I wanted to send 'application/xhtml+xml' is because the W3C semantic data extractor won't parse your page unless you send the correct content-type



    I'm wondering if/when search engines start (perhaps are presently ?) trying to parse pages for semantic content in this manner, if there will be more value in sending the correct content-type?



    thanks again everyone -Andrew

Add your comments
    Username Password
  • Format comments as (Help)