2 Replies Latest reply on Jul 27, 2011 11:04 AM by FTQuest

    buttonMode in Safari 5.1 problem

    FTQuest Level 3

      Hello there,


      This morning after updating to the latest Safari 5.1 I encountered a problem with using 'buttonMode=true": the cursor does NOT revert to default after leaving the control.

      Here is barebone example:


      <?xml version="1.0" encoding="utf-8"?>

      <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"



         minWidth="955" minHeight="600">



      <s:VerticalLayout horizontalAlign="center" gap="40" />



      <s:Button label="ButtonMode True" buttonMode="true" />

      <s:Button label="ButtonMode False" buttonMode="false" />




      I'm using OS 10.6.8


      Would appreciate any suggestion for workaround.


      Igor Borodin

        • 1. Re: buttonMode in Safari 5.1 problem
          blazejewicz Level 4

          Hi Igor,

          can you test if this is happening with consumer-grade plugin (non-debugger version) as well? There could be something with debugger version of runtime, see e.g.:


          (so you would hit issue that could be filled as bug but your customers won't)

          kind regards,


          • 2. Re: buttonMode in Safari 5.1 problem
            FTQuest Level 3

            Hi Peter,


            Thank you for the reply.

            Judging by your question I gather that you could not reproduce the problem - hand cursor not reverting to default arrow upon leaving the interactive control.

            If you couldn't, then it's indeed a relieve, because it means the problem is within my iMac.


            As to the debugger version, the problem shows up in both versions (after discovering it I reinstalled both with the latest FP).

            I also checked the behavior on couple of sites, where viewsource is enabled - like Peter deHaan's flexexamples - the same story: if 'buttonMode' is 'true', once the pointer turns into the handCursor, it does not return to default arrow.


            Please, confirm that you indeed could NOT reproduce the problem.

            BTW, it's only Safari; both Firefox and Chrome are working fine.



            Igor Borodin



            Apparently, there IS a problem: here is the thread from Apple Support Communities: