We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 22303 MODX Staff
    • 10,725 Posts
    IMO, it would be a better use of time to collaborate and find a way to make a control like this work in our trees in any browser, even if you need to work with the Ext guys to figure it out. Others will want the feature if it works for Opera; I use this in Evo frequently myself and I know many others do as well.
      • 11155
      • 74 Posts
      BTW, right-clicking in a browser to get a custom JS menu is counter-intuitive, it would indeed be better if any of those actions could be triggered by a simple left-click on a specific button/control. How do I know if some part of the displayed data should respond to a right-click ? Why some would display a contextual JS menu, whereas others would display a the browser contextual menu ? What about those extensions that add entries to the contextual menu ? Etc.
      I must say that I spent a good amount of time the first time I tried revolution, before understanding that you had to right-click on items to get a JS contextual menu undecided
        • 36416
        • 589 Posts
        Quote from: GoustiFruit at Sep 02, 2009, 03:10 AM

        BTW, right-clicking in a browser to get a custom JS menu is counter-intuitive, it would indeed be better if any of those actions could be triggered by a simple left-click on a specific button/control. How do I know if some part of the displayed data should respond to a right-click ?

        IMHO every UI element should have appropriate context menu (non-actionable elements showing application-wide actions).
          • 9670
          • 48 Posts
          Quote from: GoustiFruit at Sep 02, 2009, 03:10 AM

          BTW, right-clicking in a browser to get a custom JS menu is counter-intuitive...
          I must say that I spent a good amount of time the first time I tried revolution, before understanding that you had to right-click on items to get a JS contextual menu undecided

          I’m absolutely agree with GoustiFruit but

          Quote from: splittingred at Sep 01, 2009, 08:31 AM

          No, there is no plans to accommodate the arcane issue in Opera that disables the right-clicking...
          MODx will not, however, be accommodating the problem - so Revolution will not support Opera...

          IMO to declare cross-browser compatibility ignoring one of the most popular browsers looks a little strange. Even if this incompatibility presents in back-end only undecided
            • 9670
            • 48 Posts
            Quote from: OpenGeek at Sep 01, 2009, 06:53 PM

            IMO, it would be a better use of time to collaborate and find a way to make a control like this work in our trees in any browser, even if you need to work with the Ext guys to figure it out.

            well, if I can help, I’m ready
              • 28215
              • 4,149 Posts
              Quote from: GoustiFruit at Sep 02, 2009, 03:10 AM

              BTW, right-clicking in a browser to get a custom JS menu is counter-intuitive...
              I must say that I spent a good amount of time the first time I tried revolution, before understanding that you had to right-click on items to get a JS contextual menu undecided
              I seriously disagree - right-clicking has been a common place commodity of all native applications for a long time; see Word or Excel. You’ll start to see more and more Web Applications behaving natively (and vice versa) in the next few years, and we’re willing to help migrate users into that change.

              Secondly, this is nothing that a little end-user documentation can’t fix. Contextual menus also offer a vast new range of UI capability that icons could never offer.

              Quote from: Fil at Sep 02, 2009, 08:01 AM

              Quote from: splittingred at Sep 01, 2009, 08:31 AM

              No, there is no plans to accommodate the arcane issue in Opera that disables the right-clicking...
              MODx will not, however, be accommodating the problem - so Revolution will not support Opera...
              IMO to declare cross-browser compatibility ignoring one of the most popular browsers looks a little strange. Even if this incompatibility presents in back-end only undecided

              Opera isn’t really "one of the most popular browsers" - it’s 4th, at best, in the list, and its market share hovers around 2% of users, most of which have another browser installed on their system.

              That said, Opera has defied web standards by completely denying access to the "oncontextmenu" click event, and its user base will have to deal with that decision by its design team.

              We at Revolution are completely open to adaptations that would allow Opera to work in the manager, but we will not be compromising basic functionality for the other 98% of users because of Opera design decisions. If someone can come up with a non-intrusive solution, we’ll adopt it.
                shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
                • 11155
                • 74 Posts
                Quote from: splittingred at Sep 02, 2009, 08:25 AM

                I seriously disagree - right-clicking has been a common place commodity of all native applications for a long time; see Word or Excel. You’ll start to see more and more Web Applications behaving natively (and vice versa) in the next few years, and we’re willing to help migrate users into that change.

                What I was saying is that it is counter-intuitive in a *browser*. There are "objects" displayed on a page that we know have a possible contextual menu attached to them, like images for example, or selected text. But having dynamical objects such as those JS elements is not natural. It’s like the problem of the "back page" button on a browser, when you are loading Ajax or Flash pages, the back and forth buttons won’t work as expected.
                  • 9670
                  • 48 Posts
                  I’m not so skilled in ExtJS (I use jQuery), but I see at least 3 ways solve opera’s problem without any destructive operations.
                  1. there is wonderful button near each item in navigation tree (see pic in attachment). I suggest to use on this picture Click() event to show sub-menu only in Opera ( using construction if(Ext.isOpera) {} ). All other functionality and code will be untouched.
                  2. add additional hot-key for selected item for sub-menu, write notice for Opera user smth like ( "Select item and press Ctr-U" ) like in this solution ( http://extjs.com/forum/showthread.php?t=7526#10 ), but link to example ( http://aariadne.com/filetree ) doesn’t work in Opera sad
                  3. add ctrl+leftclick event coupled with context (right-click) event (IMO best way)

                  Every other users still can use right-click, but opera user can be happy only if a few lines will be added. Or not?
                    • 28215
                    • 4,149 Posts
                    Quote from: Fil at Sep 02, 2009, 10:35 AM

                    1. there is wonderful button near each item in navigation tree (see pic in attachment). I suggest to use on this picture Click() event to show sub-menu only in Opera ( using construction if(Ext.isOpera) {} ). All other functionality and code will be untouched.
                    Unfortunately ExtJS doesn’t allow you to assign events to the icons; just the nodes as a whole.


                    3. add ctrl+leftclick event coupled with context (right-click) event (IMO best way)
                    We’ll look into this solution. Thanks!
                      shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
                      • 30023
                      • 172 Posts
                      Quote from: splittingred at Sep 02, 2009, 08:25 AM

                      Quote from: Fil at Sep 02, 2009, 08:01 AM

                      Quote from: splittingred at Sep 01, 2009, 08:31 AM

                      No, there is no plans to accommodate the arcane issue in Opera that disables the right-clicking...
                      MODx will not, however, be accommodating the problem - so Revolution will not support Opera...
                      IMO to declare cross-browser compatibility ignoring one of the most popular browsers looks a little strange. Even if this incompatibility presents in back-end only undecided

                      Opera isn’t really "one of the most popular browsers" - it’s 4th, at best, in the list, and its market share hovers around 2% of users, most of which have another browser installed on their system.

                      That said, Opera has defied web standards by completely denying access to the "oncontextmenu" click event, and its user base will have to deal with that decision by its design team.

                      We at Revolution are completely open to adaptations that would allow Opera to work in the manager, but we will not be compromising basic functionality for the other 98% of users because of Opera design decisions. If someone can come up with a non-intrusive solution, we’ll adopt it.

                      For the record, unless I am mistaken in which case apologies in advance, "oncontextmenu" is not specified by the W3C and to use it involves defying web standards.

                      Incidentally, I have come across this after encountering an Opera/Revolution problem - I use Opera for personal use and Firefox for development due to the existence of Firebug (I have only just started using Revolution, and gather I may have another problem there). I ensure that sites I produce work in all major browsers - of which Opera is one. 2% of the internet is still alot of people, and I don’t feel that expecting them to just ’use another installed browser’ is a solution.

                      Unfortunately for those of us with this philosophy, I am getting the impression I may encounter some problems.

                      -- Tim.