e.layerX problem on Macintosh browsers

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • David Mark

    #16
    Re: e.layerX problem on Macintosh browsers

    On Oct 28, 9:21 pm, Thomas 'PointedEars' Lahn <PointedE...@we b.de>
    wrote:
    David Mark wrote:
    Thomas 'PointedEars' Lahn wrote:
    David Mark wrote:
    >On Oct 28, 4:02 am, Mathieu Maes <mathieu.m...@g mail.comwrote:
    >>behavior between the PC version and the Mac version, even though (as
    >>far as I know).
    >There are lots of little differences between FF Mac and FF Windows.
    >FF Mac has more bugs as well.
    Care to elaborate on that?
    >
    On bugs in FF Mac?  Start with the rendering woes.  Scrollbars can
    bleed through absolutely positioned elements for one.  Flash movies
    have similar problems.  [...]
    >
    Thanks, I'll keep that in mind.
    Other than those sorts of things, apps cross over to Mac pretty well
    in FF. I spent years without a Mac and now that I have one, I am
    pleased to see that most of my stuff runs perfectly on FF Mac, as well
    as Safari. I will never buy a PC again, that is for sure. I hate
    that guy.
    >
    >>I've also made the page valid XHTML. Can anyone check if this has made
    >Why?  Are you serving it as XHTML?  If so, you do know that IE will
    >open a "Save As" dialog in response to that.
    To be fair, it was something similar to XHTML in the first place, so the
    >
    That doesn't make it right.  Whenever I see this on the Web, I take it
    as a sign that the developers' only proficiency is using the
    clipboard.
    >
    Do you understand what "To be fair, ...  But yes, ..." means?  I guess
    anybody else did.
    Yes, yes, yes.
    >
    emphasis would be on "valid" now, which is in itself a Good Thing.
    >
    Valid XHTML that will ultimately be error corrected to HTML is
    useless.
    >
    That depends.  And you don't know how it is being served in this case to
    begin with.
    LOL. Would you care to place a wager on it?
    >
    But yes, XHTML should not be used unless required, even though IE/MSHTML
    will only show that dialog (hmm, you got the general meaning now ;-)) if it
    >
    You are such a pinhead.
    >
    Your smiley detector is borken.
    Are you incapable of expressing yourself in prose? :(

    And BTW, you reversed yourself on the whole "user action" argument
    here. Leave it alone.

    Comment

    • Thomas 'PointedEars' Lahn

      #17
      Re: e.layerX problem on Macintosh browsers

      Mathieu Maes wrote:
      Thomas 'PointedEars' Lahn wrote:
      >Why? Are you serving it as XHTML? If so, you do know that IE will
      >open a "Save As" dialog in response to that.
      I did not write that.
      Why not use it ? It seems to work just fine to me.
      Yes, it only seems to be so.
      I won't go into detail about this, but in my experience I found it to
      be much easier to work with. Maybe I just like my work to be more
      "stricter and cleaner" ?
      Or maybe you just didn't know what you are doing (as if that wasn't obvious
      since you had no Valid markup in the first place) because yours is a classic
      wannabe's argument. Serving XHTML 1.0 as text/html is not stricter or
      cleaner in any sense in the end than serving Valid HTML 4.01 in the first
      place. There are benefits in doing the former on the Web, but they are
      certainly not located client-side.
      Can you provide any relevant documentation that supports your
      arguments ?
      I, among others, have done that repeatedly already. STFW.
      >Works fine in Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US;
      >rv:1.9.0.3) Gecko/2008092414 Firefox/3.0.3.
      >
      Good to hear. I've got my hands on a MiniMac for now, and I can
      confirm it works in FF 3.0.3. Still no luck with Safari (version
      3.1.2) though.
      I can test it tomorrow.
      >Please read the FAQ Notes on how to quote properly:
      ><http://jibbering.com/faq/faq_notes/clj_posts.html>
      >
      Read it, don't know what I'm doing wrong... using Google Groups.
      Looks like at least partially you do know because you did not repeat the
      mistake of removing the attribution here. You should read it again to find
      out the rest; sorry, this just isn't Usenet 101.


      PointedEars
      --
      Use any version of Microsoft Frontpage to create your site.
      (This won't prevent people from viewing your source, but no one
      will want to steal it.)
      -- from <http://www.vortex-webdesign.com/help/hidesource.htm>

      Comment

      Working...