Firefox 6 breaks GWT ?

2011-08-23 Thread Roustalski 
Has anyone else noticed that text boxes do not show the focus ring
when the element has focus, and that a KeyPressEvent looking for the
charCode KeyCodes.KEY_ENTER doesn't actually work?

Why would upgrading Firefox break this functionality?

My app works on all other browsers and platforms, but upgrading FF to
version 6 breaks things? I don't understand.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Firefox 6 breaks GWT ?

2011-08-23 Thread mohit ranjan 
Also, any idea about dev mode @ FF 6 ?
Last I tried, it was not done


Mohit

On Wed, Aug 24, 2011 at 1:12 AM, Roustalski roustal...@gmail.com wrote:

 Has anyone else noticed that text boxes do not show the focus ring
 when the element has focus, and that a KeyPressEvent looking for the
 charCode KeyCodes.KEY_ENTER doesn't actually work?

 Why would upgrading Firefox break this functionality?

 My app works on all other browsers and platforms, but upgrading FF to
 version 6 breaks things? I don't understand.

 --
 You received this message because you are subscribed to the Google Groups
 Google Web Toolkit group.
 To post to this group, send email to google-web-toolkit@googlegroups.com.
 To unsubscribe from this group, send email to
 google-web-toolkit+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/google-web-toolkit?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Firefox 6 breaks GWT ?

2011-08-23 Thread Jeff Chimene 
On 08/23/2011 12:42 PM, Roustalski wrote:
 Has anyone else noticed that text boxes do not show the focus ring
 when the element has focus, and that a KeyPressEvent looking for the
 charCode KeyCodes.KEY_ENTER doesn't actually work?

Take a look at the onBrowserEvent in
com.google.gwt.cell.client.EditTextCell.class

I see:
boolean enterPressed = keyup.equals(type)
   keyCode == KeyCodes.KEY_ENTER;

and the edit mode of EditTextCell works for me. So, maybe rewrite the
logic you're using. This code seems to have survived the transition to FF6.

 Why would upgrading Firefox break this functionality?
 
 My app works on all other browsers and platforms, but upgrading FF to
 version 6 breaks things? I don't understand.
 

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Firefox 6 breaks GWT ?

2011-08-23 Thread Roustalski 
Thanks for your response, but I'm confused.

I'm using com.google.gwt.user.client.ui.TextBox.

Here is the event handler that I'm using:

@UiHandler( tbName )
void onTbNameKeyPress( KeyPressEvent event )
{
Log.info( Event char code:  +
String.valueOf( event.getCharCode() ) );
//event.getNativeEvent().
if ( event.getNativeEvent().getCharCode() == KeyCodes.KEY_ENTER 
)
// ...
}

I've also tried event.getCharCode() and it also fails. This works on
Safari, FF = 5, and Chrome on MAC OSX.

Is my logic wrong? Why do I need to use specific code for a particular
version of a browser?

On Aug 23, 3:52 pm, Jeff Chimene jchim...@gmail.com wrote:
 On 08/23/2011 12:42 PM, Roustalski wrote:

  Has anyone else noticed that text boxes do not show the focus ring
  when the element has focus, and that a KeyPressEvent looking for the
  charCode KeyCodes.KEY_ENTER doesn't actually work?

 Take a look at the onBrowserEvent in
 com.google.gwt.cell.client.EditTextCell.class

 I see:
 boolean enterPressed = keyup.equals(type)
            keyCode == KeyCodes.KEY_ENTER;

 and the edit mode of EditTextCell works for me. So, maybe rewrite the
 logic you're using. This code seems to have survived the transition to FF6.







  Why would upgrading Firefox break this functionality?

  My app works on all other browsers and platforms, but upgrading FF to
  version 6 breaks things? I don't understand.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Firefox 6 breaks GWT ?

2011-08-23 Thread Jeff Chimene 
On 08/23/2011 02:38 PM, Roustalski wrote:
 Thanks for your response, but I'm confused.
 
 I'm using com.google.gwt.user.client.ui.TextBox.
 
 Here is the event handler that I'm using:
 
 @UiHandler( tbName )
   void onTbNameKeyPress( KeyPressEvent event )
   {
   Log.info( Event char code:  +
 String.valueOf( event.getCharCode() ) );
   //event.getNativeEvent().
   if ( event.getNativeEvent().getCharCode() == KeyCodes.KEY_ENTER 
 )

I'd suggest using getKeyCode() instead of getCharCode()


   // ...
   }
 
 I've also tried event.getCharCode() and it also fails. This works on
 Safari, FF = 5, and Chrome on MAC OSX.
 
 Is my logic wrong? Why do I need to use specific code for a particular
 version of a browser?
 
 On Aug 23, 3:52 pm, Jeff Chimene jchim...@gmail.com wrote:
 On 08/23/2011 12:42 PM, Roustalski wrote:

 Has anyone else noticed that text boxes do not show the focus ring
 when the element has focus, and that a KeyPressEvent looking for the
 charCode KeyCodes.KEY_ENTER doesn't actually work?

 Take a look at the onBrowserEvent in
 com.google.gwt.cell.client.EditTextCell.class

 I see:
 boolean enterPressed = keyup.equals(type)
keyCode == KeyCodes.KEY_ENTER;

 and the edit mode of EditTextCell works for me. So, maybe rewrite the
 logic you're using. This code seems to have survived the transition to FF6.







 Why would upgrading Firefox break this functionality?

 My app works on all other browsers and platforms, but upgrading FF to
 version 6 breaks things? I don't understand.
 

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Firefox 6 breaks GWT ?

2011-08-23 Thread Roustalski 
com.google.gwt.event.dom.client.KeyPressEvent.class only has a
getCharCode method and does not have a getKeyCode method.

On Aug 23, 4:48 pm, Jeff Chimene jchim...@gmail.com wrote:
 On 08/23/2011 02:38 PM, Roustalski wrote:

  Thanks for your response, but I'm confused.

  I'm using com.google.gwt.user.client.ui.TextBox.

  Here is the event handler that I'm using:

          @UiHandler( tbName )
     void onTbNameKeyPress( KeyPressEvent event )
     {
             Log.info( Event char code:  +
  String.valueOf( event.getCharCode() ) );
             //event.getNativeEvent().
             if ( event.getNativeEvent().getCharCode() == KeyCodes.KEY_ENTER )

 I'd suggest using getKeyCode() instead of getCharCode()







                     // ...
     }

  I've also tried event.getCharCode() and it also fails. This works on
  Safari, FF = 5, and Chrome on MAC OSX.

  Is my logic wrong? Why do I need to use specific code for a particular
  version of a browser?

  On Aug 23, 3:52 pm, Jeff Chimene jchim...@gmail.com wrote:
  On 08/23/2011 12:42 PM, Roustalski wrote:

  Has anyone else noticed that text boxes do not show the focus ring
  when the element has focus, and that a KeyPressEvent looking for the
  charCode KeyCodes.KEY_ENTER doesn't actually work?

  Take a look at the onBrowserEvent in
  com.google.gwt.cell.client.EditTextCell.class

  I see:
  boolean enterPressed = keyup.equals(type)
             keyCode == KeyCodes.KEY_ENTER;

  and the edit mode of EditTextCell works for me. So, maybe rewrite the
  logic you're using. This code seems to have survived the transition to FF6.

  Why would upgrading Firefox break this functionality?

  My app works on all other browsers and platforms, but upgrading FF to
  version 6 breaks things? I don't understand.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Firefox 6 breaks GWT ?

2011-08-23 Thread Jeff Chimene 
On 08/23/2011 03:00 PM, Roustalski wrote:
 com.google.gwt.event.dom.client.KeyPressEvent.class only has a
 getCharCode method and does not have a getKeyCode method.

That may be, but you're asking for the underlying NativeEvent, which
does have a getKeyCode()

 
 On Aug 23, 4:48 pm, Jeff Chimene jchim...@gmail.com wrote:
 On 08/23/2011 02:38 PM, Roustalski wrote:

 Thanks for your response, but I'm confused.

 I'm using com.google.gwt.user.client.ui.TextBox.

 Here is the event handler that I'm using:

 @UiHandler( tbName )
void onTbNameKeyPress( KeyPressEvent event )
{
Log.info( Event char code:  +
 String.valueOf( event.getCharCode() ) );
//event.getNativeEvent().
if ( event.getNativeEvent().getCharCode() == KeyCodes.KEY_ENTER )

 I'd suggest using getKeyCode() instead of getCharCode()







// ...
}

 I've also tried event.getCharCode() and it also fails. This works on
 Safari, FF = 5, and Chrome on MAC OSX.

 Is my logic wrong? Why do I need to use specific code for a particular
 version of a browser?

 On Aug 23, 3:52 pm, Jeff Chimene jchim...@gmail.com wrote:
 On 08/23/2011 12:42 PM, Roustalski wrote:

 Has anyone else noticed that text boxes do not show the focus ring
 when the element has focus, and that a KeyPressEvent looking for the
 charCode KeyCodes.KEY_ENTER doesn't actually work?

 Take a look at the onBrowserEvent in
 com.google.gwt.cell.client.EditTextCell.class

 I see:
 boolean enterPressed = keyup.equals(type)
keyCode == KeyCodes.KEY_ENTER;

 and the edit mode of EditTextCell works for me. So, maybe rewrite the
 logic you're using. This code seems to have survived the transition to FF6.

 Why would upgrading Firefox break this functionality?

 My app works on all other browsers and platforms, but upgrading FF to
 version 6 breaks things? I don't understand.
 

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Firefox 6 breaks GWT ?

2011-08-23 Thread Roustalski 
Thanks!

Do you have any information as to why FF wouldn't behave the same as
the other browsers?

On Aug 23, 5:04 pm, Jeff Chimene jchim...@gmail.com wrote:
 On 08/23/2011 03:00 PM, Roustalski wrote:

  com.google.gwt.event.dom.client.KeyPressEvent.class only has a
  getCharCode method and does not have a getKeyCode method.

 That may be, but you're asking for the underlying NativeEvent, which
 does have a getKeyCode()









  On Aug 23, 4:48 pm, Jeff Chimene jchim...@gmail.com wrote:
  On 08/23/2011 02:38 PM, Roustalski wrote:

  Thanks for your response, but I'm confused.

  I'm using com.google.gwt.user.client.ui.TextBox.

  Here is the event handler that I'm using:

          @UiHandler( tbName )
     void onTbNameKeyPress( KeyPressEvent event )
     {
             Log.info( Event char code:  +
  String.valueOf( event.getCharCode() ) );
             //event.getNativeEvent().
             if ( event.getNativeEvent().getCharCode() == 
  KeyCodes.KEY_ENTER )

  I'd suggest using getKeyCode() instead of getCharCode()

                     // ...
     }

  I've also tried event.getCharCode() and it also fails. This works on
  Safari, FF = 5, and Chrome on MAC OSX.

  Is my logic wrong? Why do I need to use specific code for a particular
  version of a browser?

  On Aug 23, 3:52 pm, Jeff Chimene jchim...@gmail.com wrote:
  On 08/23/2011 12:42 PM, Roustalski wrote:

  Has anyone else noticed that text boxes do not show the focus ring
  when the element has focus, and that a KeyPressEvent looking for the
  charCode KeyCodes.KEY_ENTER doesn't actually work?

  Take a look at the onBrowserEvent in
  com.google.gwt.cell.client.EditTextCell.class

  I see:
  boolean enterPressed = keyup.equals(type)
             keyCode == KeyCodes.KEY_ENTER;

  and the edit mode of EditTextCell works for me. So, maybe rewrite the
  logic you're using. This code seems to have survived the transition to 
  FF6.

  Why would upgrading Firefox break this functionality?

  My app works on all other browsers and platforms, but upgrading FF to
  version 6 breaks things? I don't understand.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Firefox 6 breaks GWT ?

2011-08-23 Thread Jeff Chimene 
On 08/23/2011 03:45 PM, Roustalski wrote:
 Thanks!
 
 Do you have any information as to why FF wouldn't behave the same as
 the other browsers?

Well, I'd prefer to rephrase the question: Why don't the other browsers
behave like FF? :)

Nevertheless, I have no idea why it suddenly broke. I suppose you could
dig through bugzilla, but I'd accept victory and move on...

 
 On Aug 23, 5:04 pm, Jeff Chimene jchim...@gmail.com wrote:
 On 08/23/2011 03:00 PM, Roustalski wrote:

 com.google.gwt.event.dom.client.KeyPressEvent.class only has a
 getCharCode method and does not have a getKeyCode method.

 That may be, but you're asking for the underlying NativeEvent, which
 does have a getKeyCode()









 On Aug 23, 4:48 pm, Jeff Chimene jchim...@gmail.com wrote:
 On 08/23/2011 02:38 PM, Roustalski wrote:

 Thanks for your response, but I'm confused.

 I'm using com.google.gwt.user.client.ui.TextBox.

 Here is the event handler that I'm using:

 @UiHandler( tbName )
void onTbNameKeyPress( KeyPressEvent event )
{
Log.info( Event char code:  +
 String.valueOf( event.getCharCode() ) );
//event.getNativeEvent().
if ( event.getNativeEvent().getCharCode() == 
 KeyCodes.KEY_ENTER )

 I'd suggest using getKeyCode() instead of getCharCode()

// ...
}

 I've also tried event.getCharCode() and it also fails. This works on
 Safari, FF = 5, and Chrome on MAC OSX.

 Is my logic wrong? Why do I need to use specific code for a particular
 version of a browser?

 On Aug 23, 3:52 pm, Jeff Chimene jchim...@gmail.com wrote:
 On 08/23/2011 12:42 PM, Roustalski wrote:

 Has anyone else noticed that text boxes do not show the focus ring
 when the element has focus, and that a KeyPressEvent looking for the
 charCode KeyCodes.KEY_ENTER doesn't actually work?

 Take a look at the onBrowserEvent in
 com.google.gwt.cell.client.EditTextCell.class

 I see:
 boolean enterPressed = keyup.equals(type)
keyCode == KeyCodes.KEY_ENTER;

 and the edit mode of EditTextCell works for me. So, maybe rewrite the
 logic you're using. This code seems to have survived the transition to 
 FF6.

 Why would upgrading Firefox break this functionality?

 My app works on all other browsers and platforms, but upgrading FF to
 version 6 breaks things? I don't understand.
 

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Firefox 6 breaks GWT ?

2011-08-23 Thread Thomas Broyer 
When it comes to keyboard events, IE behavior is the saner and better, and 
Firefox's is the one you wish never existed.

As for the enter key in Firefox, it doesn't work in either Firefox version, 
at least on Windows and Linux: 
http://code.google.com/p/google-web-toolkit/issues/list?can=2q=keypresshandler
It used to work in previous versions of *GWT*, but had many bugs in other 
cases.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/ddXRGsATuOQJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Firefox 6 breaks GWT ?

2011-08-23 Thread mP 
Hiho

Some of the replies here give suggestions seem to imply there might be
a mistake between comparisons between characters and keycodes. I have
created an issue that suggests that helpers be added to the event
classes to assist these very comparisons. If you like the idea plz
vote for it.

http://code.google.com/p/google-web-toolkit/issues/detail?id=6395

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.