Re: Reason for disabling Debug IDs in production?

2nd Try :)

On Tue, Feb 16, 2016 at 1:11 PM, Gourab Panda <gourab.p@gmail.com> wrote:

Hi,

In out Team, QA(testers) thinks that disabling the 'debugid' during production build means they are delivering different build to customer.

I can think of 2 reason why we usually disable it during production:

1- The JavaScript download and processing of 'ensureDebugId()' is an unwanted overhead

2- when we set fixed dubug Id, someone can easily inject Unwanted script, which can make use of this ID. (Not sure who the injection will work though.)

Is there any other reason why we disable Debug Ids in production ?

Regards

Gourab.

--
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.