1 Reply Latest reply on Feb 6, 2008 10:05 AM by Florian Marwede

    Opera compatibility

    Soul Spirit Newbie

      Hi. I played with RichFaces (3.1.4) for the first time in the last several days, and I have to say that they're a great addition to the standard jsf tag library.

      Although the default components and themes satisfies the needs for my current application, I'm very disappointed about the declared cross-browser compatibility (http://labs.jboss.com/file-access/default/members/jbossrichfaces/freezone/docs/devguide/en/html/TechnicalRequirements.html).

      I develop using Opera as main browser, and I found evident glitches in my first walkthrough of the library.
      I don't know who could proudly claim such browser compatibility even without running any simple test case on each browser.

      Some problems I've discovered within the first 5 minutes using each of the following components:

      rich:dropDownMenu object generates visual glitches, caused by a javascript error I've not investigated

      Event thread: mouseout
      name: TypeError
      message: Statement on line 95: Type mismatch (usually a non-object value used where an object is required)
       Line 95 of linked script http://***/a4j_3_1_4.GAscripts/menu.js.faces
       var within = false;
      var targetElement = event.relatedTarget;
      var srcElement = Event.element(event);
      if (targetElement)
       Line 79 of linked script http://***/a4j_3_1_4.GAscripts/menu.js.faces
       if (options.disabled == false && ! RichFaces.Menu.isWithin(e, $(topLevel)))
       Line 82 of linked script http://***/a4j_3_1_4.GAscripts/menu.js.faces
       menuOff.call(this, e);
      mouseout.call(this, e);
       Line 18 of linked script http://***/a4j_3_1_4.GAorg.ajax4jsf.javascript.PrototypeScript.faces
       return __method.apply(object, [event || window.event].concat(args));
       Line 242 of linked script http://***/a4j_3_1_4.GAorg.ajax4jsf.javascript.PrototypeScript.faces
       return false;
      handler.call(element, event);
       At unknown location
       [statement source code not available]

      Letting the user play with a rich:suggestionbox, prevents him to succesfully submit a form (in certain not better defined circumstances), with no indication about any error. Simply, the submit button doesn't trigger any action...

        • 1. Re: Opera compatibility
          Florian Marwede Expert

          There are several specific opera bugs in JIRA which should be solved with 3.2.0 GA. So the compatibility with Opera is theoretically given with defining each incompatibility as bug ;-)

          Currently I count 9 open bugs concerning Opera but on first glance the problems you mentioned are not already there. So feel free to add JIRA issues.