Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Bug? HTML in IE contains tag </nobr/>

    -Open http://www.smartclient.com/smartgwt/showcase/#featured_tree_grid in Internet Explorer 9

    -Open Developer Tools (press F12)

    -Use the white arrow to select the text "Charles Madigen" in the TreeGrid

    -The HTML tab in developer tools now shows the tag </nobr/>

    This confuses Selenium, e.g., and I had to use a workaround.

    #2
    Hello, please don't report any bugs by testing solely in the online Showcase - use the latest patched build (see smartclient.com/builds).

    Comment


      #3
      Reproducible with 3.1d (2012-08-14).

      Comment


        #4
        We don't actually write out that HTML, it looks to be an artifact of the tool that it shows this invalid tag.

        We may attempt a workaround if it's low effort and safe, but since this is harmless we will most likely leave it alone.

        Comment


          #5
          Interesting.
          We don't actually write out "</nobr/>" - this is the browser's interpretation of a standard closing nobr tag in this particular DOM structure.

          However we've reviewed the code and have determined that we can safely remove this particular tag altogether, which gets rid of this strange reported element in the Developer Tools in IE9.

          This change will be present in the next nightly build 3.1d branch. If this doesn't resolve the problem for you, please let us know

          Thanks
          Isomorphic Software

          Comment


            #6
            Still there in SNAPSHOT_v8.3d_2012-08-27/LGPL Development Only (built 2012-08-27)...?!?

            Well, maybe as an alternative to changing the HTML you write out, posting a bug report about IE9 would be appropriate?

            Comment


              #7
              It seems you are writing out nested <nobr> elements for grid cells, and this confuses IE. (SmartGWT 3.1)

              I tested this by editing a local HTML page (based on what you supposedly write out for tree grid cells) and viewing the results of the Selenium method calls WebElement.getAttribute("innerHTML"), WebElement.getText() and WebElement.findElements(By.xpath("child::*")). None of the results is correct.
              Last edited by mec; 19 Feb 2013, 07:18.

              Comment


                #8
                Can you tells us what document mode (visible in the F12 tools) you're using at the time you see the problem (i.e. Quirks Mode, IE9 Standards Mode, etc.), and the version of 3.1 that you're currently using?
                Last edited by Isomorphic; 19 Feb 2013, 13:34.

                Comment


                  #9
                  I used the SmartGWT 3.1 version that had been available via the online showcase at the date I posted (or maybe a few days before).

                  When loading the showcase, document mode becomes Quirks.

                  Comment


                    #10
                    There are two issues here:
                    - Whether we write out nested <nobr> tags
                    - The claim that it "confuses" IE9 and/or Selenium WebDriver

                    The first statement is correct for IE8/9 Quirks Modes. We do write out nested <nobr> tags, but have so far not observed any untoward effects on the functionality of SmartClient code. For IE8/9 Standards Mode, we avoid this, so this may be an option for you. (You can change the doctype of the showcase by editing the root html page if you wish.)

                    As to the second, we would direct you to read the reference topic UsingSelenium, of which an important statement is:

                    Code:
                    XPath based locators are extremely fragile due to complexity
                    of certain highly nested DOM elements you need access to
                    combined with the fact that XPath support varies across
                    browsers and so your tests might not work across different
                    browsers.
                    You should be using scLocators, rather than Xpaths, and for SC8.3/SGWT3.1 we support this in Selenium RC (v1), but not Selenium (v2) WebDriver. We support being able to record your Selenium scripts in Firefox Selenium IDE, and being able to play them back in IE/Firefox/Chrome.

                    Comment

                    Working...
                    X