search

datni / gwt-pectin

Automatically exported from code.google.com/p/gwt-pectin
0 stars 0 forks source link

Validation with model.var.addValueChangeHandler() doesn't work for Chrome with AutoFill #32

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create a GWT-form with Model (FieldModel<String> model.email) and View 
(TextBox email) and an input field with name attribute (name="email")
2. Add ValueChangeHandler (model.email.addValueChangeHandler) which validates 
the field
3. Activate Chromes AutoFill with Options->Privacy->activate AutoFill
4. Open Form in Chrome
5. click inside the input field, so that AutoFill Text will be shown and select 
it. tab out of the field (blur)

What is the expected output? What do you see instead?
Other Browsers will validate the field, but not the Chrome Browser

What version of the product are you using? On what operating system?
gwt-pectin 0.7 with Windows, Linux and Mac

Please provide any additional information below.
Summary:
The entered AutoFill value in Chrome won't be validated

Original issue reported on code.google.com by stefan.k...@gtempaccount.com on 28 Jul 2010 at 7:50

GoogleCodeExporter commented 8 years ago 
This sounds like it might be an issue with TextBox not firing ValueChangeEvents 
on autofill in Chrome.  If so then it would be better to post this as either a 
Chrome or GWT bug.

Can you test if the TextBox is firing ValueChanageEvents on autofill?

Original comment by andrew.pietsch on 28 Jul 2010 at 8:41

GoogleCodeExporter commented 8 years ago 
not even the direct ValueChangeEvent on a TextBox si firing.
So you're right. It's a GWT- or Chrome-Bug.
I'm wondering because both is google.

Original comment by stefan.k...@gtempaccount.com on 28 Jul 2010 at 10:58

GoogleCodeExporter commented 8 years ago 
Yep, I'd suspect it's a Chrome issue.  It's a very difficult and annoying one 
since pectin relies on value change events.  I'm not really sure of a solution 
at the current point in time other than some kind of hack to fire value change 
events.

Original comment by andrew.pietsch on 28 Jul 2010 at 11:49

GoogleCodeExporter commented 8 years ago 
it's really a Chrome issue.
This issue can be closed

Original comment by stefan.k...@gtempaccount.com on 18 Apr 2011 at 9:11