Re: Veracode detected 5 XSS issues in nocache.js

module.nocache.js is a build artifact, created with GWT. Like all web technologies it's up to the developer using GWT to ensure vulnerabilities like XSS are not introduced.

There's further information about avoiding the introduction of XSS vulnerabilities in GWT applications here:

http://www.gwtproject.org/doc/latest/DevGuideSecuritySafeHtml.html

On 19 Feb 2020, at 06:33, kaveri <dusanekaveri@gmail.com> wrote:

Veracode has reported 5 places with error - improper neutralization of script related hrml tags in web page(basic xss) in module.nocache.js at line number 4, 10, 9 and 13

Is there any fix to this issue or proper explanation to prove that code is secured

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/49e6d69a-fc94-42e1-b70b-14a550044d03%40googlegroups.com.

Veracode detected 5 XSS issues in nocache.js

Veracode has reported 5 places with error - improper neutralization of script related hrml tags in web page(basic xss) in module.nocache.js at line number 4, 10, 9 and 13

Is there any fix to this issue or proper explanation to prove that code is secured

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/49e6d69a-fc94-42e1-b70b-14a550044d03%40googlegroups.com.

Re: Is GWT 3.0 /GWT 2.9 dead?

Frank - Thanks for the reply, but it would be good to understand the plans to complete the GWT 2.9 release - particularly with reference to Java 11 support.  Any insight there?

On Monday, January 27, 2020 at 4:23:09 AM UTC-5, Frank Hossfeld wrote:

Atm the community is very active. We are working on GWT modules: replacing generators and JSNI, testig the migraed moules against J2CL, etc.

Besides that, many new frameworks are evolving.

Take a look at this rooms:
https://gitter.im/gwtproject/gwt

https://gitter.im/vertispan/j2cl

https://gitter.im/DominoKit/domino

to get more infos.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/61ae1f73-9bdb-4131-9ccc-f27808e44437%40googlegroups.com.

Re: How to correct IE font size problem?

I know this is old stuff.. but just had to say..  the page zoom worked fine for me..  Yes, fonts vary per browser, but when your talking 20% bigger.. then check the page zoom...just saying

On Thursday, March 4, 2010 at 3:57:08 PM UTC-5, Sorinel C wrote:

Are you sure isn't it the IE8 option "Page ~ Zoom" set to 150% instead
100% ?

Cheers!

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/d80bd082-2c60-4ee4-99de-aa55c7bb9046%40googlegroups.com.

Re: i18n Failing

<set-property name="locale" value="en,es" />

That fixed it. Thanks.

On Friday, January 31, 2020 at 5:11:28 AM UTC-8, Thomas Broyer wrote:

You'll want to

<set-property name="locale" value="en,es" />

The reason for this set-property is to remove the "default" value from the available values (the locale property is defined with a single "default" initial value, you later extend it to add en and es, so it's now default,en,es, and then you overwrite it with this set-property to just en,es).

Actually, if you support an English locale, you don't really need the remove the "default" value, as it'll be equivalent to "en" (in most cases at least) thus won't produce an additional permutation anyway. To make it work though, you need to put your English translations in the FixedStrings (or other localizable interfaces) annotations and/or in the non-suffixed .properties file (i.e. rename FixedStrings_en.properties to FixedStrings.properties).

On Friday, January 31, 2020 at 10:36:48 AM UTC+1, Andrew Buck wrote:

I am trying to add a second locale to my GWT app, but I'm unable to make it work.

Up until now, I've had:

<extend-property name="locale" values="en" />
<set-property name="locale" value="en" />
<set-property-fallback name="locale" value="en"/>

And now if I change it to:

<extend-property name="locale" values="en,es" />
<set-property name="locale" value="en" />
<set-property-fallback name="locale" value="en"/>

And add a tag in the page header:

<meta name='gwt:property' content='locale=es'/>

I still always see the page in English.

If I instead do:

<extend-property name="locale" values="en,es" />
<set-property name="locale" value="es" />
<set-property-fallback name="locale" value="en"/>

Then I always see the page in Spanish.

The <set-property...> tag is not shown in the GWT documentation, but if I remove it, then I get a compile error: 
"Failed to resolve '[package-name].i18n.FixedStrings' via deferred binding"

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/92a402a6-d15d-46ec-8b3d-699dc7ca1bbd%40googlegroups.com.

Re: i18n Failing

Hi,

For EN and DE I have the following

<!-- Locale -->

<inherits name="com.google.gwt.i18n.I18N" />

<!-- German language, independent of country -->

<extend-property name="locale" values="de" />

<extend-property name='locale' values='de_DE' />

<!-- English language, independent of country -->

<extend-property name="locale" values="en" />

<set-property-fallback name='locale' value='en' />

<set-property name='locale' value='de_DE' />

extend-property - add support for a specific locale, set-property, in the end, sets the "default" locale. 

Best,

Stas

On Friday, January 31, 2020 at 10:36:48 AM UTC+1, Andrew Buck wrote:

I am trying to add a second locale to my GWT app, but I'm unable to make it work.

Up until now, I've had:

<extend-property name="locale" values="en" />
<set-property name="locale" value="en" />
<set-property-fallback name="locale" value="en"/>

And now if I change it to:

<extend-property name="locale" values="en,es" />
<set-property name="locale" value="en" />
<set-property-fallback name="locale" value="en"/>

And add a tag in the page header:

<meta name='gwt:property' content='locale=es'/>

I still always see the page in English.

If I instead do:

<extend-property name="locale" values="en,es" />
<set-property name="locale" value="es" />
<set-property-fallback name="locale" value="en"/>

Then I always see the page in Spanish.

The <set-property...> tag is not shown in the GWT documentation, but if I remove it, then I get a compile error: 
"Failed to resolve '[package-name].i18n.FixedStrings' via deferred binding"

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/4c8d0d55-723d-45e6-92fb-927e511637ce%40googlegroups.com.

Re: i18n Failing

You'll want to

<set-property name="locale" value="en,es" />

The reason for this set-property is to remove the "default" value from the available values (the locale property is defined with a single "default" initial value, you later extend it to add en and es, so it's now default,en,es, and then you overwrite it with this set-property to just en,es).

Actually, if you support an English locale, you don't really need the remove the "default" value, as it'll be equivalent to "en" (in most cases at least) thus won't produce an additional permutation anyway. To make it work though, you need to put your English translations in the FixedStrings (or other localizable interfaces) annotations and/or in the non-suffixed .properties file (i.e. rename FixedStrings_en.properties to FixedStrings.properties).

On Friday, January 31, 2020 at 10:36:48 AM UTC+1, Andrew Buck wrote:

I am trying to add a second locale to my GWT app, but I'm unable to make it work.

Up until now, I've had:

<extend-property name="locale" values="en" />
<set-property name="locale" value="en" />
<set-property-fallback name="locale" value="en"/>

And now if I change it to:

<extend-property name="locale" values="en,es" />
<set-property name="locale" value="en" />
<set-property-fallback name="locale" value="en"/>

And add a tag in the page header:

<meta name='gwt:property' content='locale=es'/>

I still always see the page in English.

If I instead do:

<extend-property name="locale" values="en,es" />
<set-property name="locale" value="es" />
<set-property-fallback name="locale" value="en"/>

Then I always see the page in Spanish.

The <set-property...> tag is not shown in the GWT documentation, but if I remove it, then I get a compile error: 
"Failed to resolve '[package-name].i18n.FixedStrings' via deferred binding"

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/4736124a-85d1-46a4-adab-8bcee2bcf400%40googlegroups.com.