Page 2 of 2 FirstFirst 12
Results 11 to 15 of 15

Thread: new chrome 24.X version problems

  1. #11
    Sencha User
    Join Date
    Jun 2010
    Posts
    18
    Answers
    2
    Vote Rating
    0
      0  

    Default

    Well is probably some miss config to the jar dependencies,
    but if its working then its not important.

    Cheers,
    Baze

  2. #12
    Sencha - GXT Dev Team
    Join Date
    Feb 2009
    Location
    Minnesota
    Posts
    2,737
    Answers
    109
    Vote Rating
    93
      0  

    Default

    The warning shown looks like it is coming from the GWT class NamedFrame, which you may be using somewhere in your application. In GWT 2.5.0 it seems to have been changed to use a SafeHtmlTemplates instance to draw the iframe more easily, and apparently the template isn't completely safe according to the built-in rules. That said, since the argument to be passed into that template is always the string "javascript:''", there is no way that this particular issue can be made unsafe.

    This is never created directly from within GWT or GXT, so I suspect you'll find it created somewhere in your codebase. It is likely that you can use another GWT class, Frame instead, which should not emit this warning, but I can't be certain about this without seeing your code. It may be that this NamedFrame is being created within a UiBinder xml file, so you'll need to check them as well.

    It appears thought it should be safe to ignore this warning, but you might find it easier to just change out that instance for a different frame.

  3. #13
    Sencha User
    Join Date
    Jul 2009
    Location
    Trabzon
    Posts
    101
    Vote Rating
    0
      0  

    Default

    Hi Colin,

    thanks for your detailed explanation,

    I scanned my projects from beginning to end, at last I found the cause of this warning.

    I used NamedFrame when I download a file, with hidden iframe.

    Code:
    
        public static void downloadFile( String url)
        {
            boolean frameExists = ( RootPanel.get( "downloadiframe" ) != null );
            if ( frameExists ) {
                Widget widgetFrame = (Widget) RootPanel.get( "downloadiframe" );
                widgetFrame.removeFromParent();
            }
            
            NamedFrame frame = new NamedFrame( "downloadiframe" );
            frame.setUrl( url );
            frame.setVisible( false );
            
            RootPanel.get().add( frame );
        }
    Now I replaced my code like following:

    Code:
    
        public static void downloadFile( String url)
        {
            if ( downloadFrame != null ) downloadFrame.removeFromParent();
            downloadFrame = new Frame( url );
            downloadFrame.setVisible( false );
            RootPanel.get().add( downloadFrame );
        }
    And I got rid of this compiler warning.

    Thanks a lot for this hint!
    Website: harunates.com
    Feel free to contact me harun@harunates.com

  4. #14
    Sencha - GXT Dev Team
    Join Date
    Feb 2009
    Location
    Minnesota
    Posts
    2,737
    Answers
    109
    Vote Rating
    93
      0  

    Default

    This patch to GWT will prevent that compiler warning from happening in future versions of GWT: https://gwt-review.googlesource.com/#/c/1800/

    Not my doing, I just happened to see it in my inbox this morning along with your post.

  5. #15
    Sencha User
    Join Date
    Jul 2009
    Location
    Trabzon
    Posts
    101
    Vote Rating
    0
      0  

    Default

    Colin, they're too late aren't they?

    so unlucky to me, I have already solved it...

    Forget whatever...
    Website: harunates.com
    Feel free to contact me harun@harunates.com

Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •