Announcement

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

    Summary Row Formatting Disappears on Click

    Using: SmartGWT 3.0 with SmartClient Version: v8.2p_2012-07-30/LGPL Development Only (built 2012-07-30) and any browser. See attached for example code.

    When using a summaryRowDataSource on a ListGrid, if you click on the summary row the font-weight changes from "bold" to "normal" for some reason. If you comment out the setSummaryRowDataSource() line then the font-weight stops changing when you click on the summary row.

    Also attached is an example screenshot of what happens (before the click on the left, after on the right).

    Is there anything in the CSS we can do to prevent this from happening?
    Attached Files

    #2
    This isn't an already fixed issue somewhere is it? I tried googling for similar problems but nothing turned up. The example I provided is about as basic as it gets, is there any other information I need to provide?

    Comment


      #3
      Is my SmartGWT version to far out of date to get an answer on this? I know my example is sufficient (even though it has yet to be looked at at this point in time). Is this a known issue or has it been fixed in more recent versions? If so, knowing which version I'll have to upgrade to would be nice to know.

      Thanks.

      Comment


        #4
        You didn't mention what browser(s) and versions, what skin the issue happens in, or whether you have any external CSS styling (which is a likely culprit).

        And yes, you should try the latest.

        Comment


          #5
          Originally posted by PhoenixClearwater View Post
          Using: SmartGWT 3.0 with SmartClient Version: v8.2p_2012-07-30/LGPL Development Only (built 2012-07-30) and any browser.
          Thank you for the reply, I did mention what browsers and versions. The version I forgot to mention was the GWT version which is 2.3. Everything I was using was SmartGWT default (so Enterprise Blue theme with no custom CSS). The example code in my first post is the only custom code writen.

          My Main.gwt.xml file (if it matters) is:
          Code:
          <module>
          	<inherits name="com.google.gwt.user.User"/>	
          	<inherits name="com.smartgwt.SmartGwt"/>
          	<inherits name="com.smartgwt.tools.SmartGwtTools" />
          	<inherits name="com.google.gwt.http.HTTP" />
          	<entry-point class="...MainEntryPoint"/>
          </module>

          Comment


            #6
            Sorry, with dozens of combinations of browsers, browser versions and OS platforms, we don't really take "any browser" seriously. Can you at least indicate any one browser, version and platform where you can definitely get this effect? And ideally some others where it also happens.

            Comment


              #7
              Well, you're right, I guess I can't literally mean any browser/os. But I'm sure I'm not lying when I say that. I was specifically testing on Win 7 using IE9 (in IE8 compatability mode), FF11, and Chrome. I also just had a coworker reproduce it in FF15, Chrome, and Konqueror9 on Ubuntu.
              Last edited by PhoenixClearwater; 24 Oct 2012, 14:49.

              Comment


                #8
                Thanks, we'll take a look.

                Just to clarify, it's a routine thing that someone mentions they tested on "Firefox" and we can't reproduce the problem, then it turns out it's OS-specific eg MacOS only, a very old or pre-release version of the browser, etc. That's why we insist on the exact environment.

                Comment


                  #9
                  Since it has been a few days I'm curious if any progress has been made on this yet?

                  Thanks.

                  Comment


                    #10
                    Was it not possible to reproduce this issue? I'm wondering why there hasn't been more feedback on this now that you seem to have all the information you need.

                    Comment


                      #11
                      Just checking in again. Last I heard this issue was being looked into and I just need to know if there is anything else I can do to get a resolution on it.

                      Thanks.

                      Comment


                        #12
                        It queued to be looked at, but it's cosmetic and obscure so it keeps getting bumped by more significant issues.

                        Purchasing support is one way to make sure it gets looked at within a specific timeframe.

                        Comment

                        Working...
                        X