From: Leif Åstrand <leif@vaadin.com>
Date: Wed, 11 Nov 2015 12:16:42 +0000 (+0000)
Subject: Fix outdated javadoc reference
X-Git-Tag: 7.6.0.beta2~41
X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=142f7dcebb249c9c458cdbade014212b1a9ac27d;p=vaadin-framework.git

Fix outdated javadoc reference

Change-Id: I0bfae621ca71df02e5e19c33d4c21498fa86616c
---

diff --git a/server/src/com/vaadin/ui/AbstractTextField.java b/server/src/com/vaadin/ui/AbstractTextField.java
index 93025ac0fd..5fbe60937a 100644
--- a/server/src/com/vaadin/ui/AbstractTextField.java
+++ b/server/src/com/vaadin/ui/AbstractTextField.java
@@ -510,7 +510,7 @@ public abstract class AbstractTextField extends AbstractField<String> implements
         /**
          * Each text change event in the UI causes the event to be communicated
          * to the application after a timeout. The length of the timeout can be
-         * controlled with {@link TextField#setInputEventTimeout(int)}. Only the
+         * controlled with {@link TextField#setTextChangeTimeout(int)}. Only the
          * last input event is reported to the server side if several text
          * change events happen during the timeout.
          * <p>
@@ -523,7 +523,7 @@ public abstract class AbstractTextField extends AbstractField<String> implements
         /**
          * An event is triggered when there is a pause of text modifications.
          * The length of the pause can be modified with
-         * {@link TextField#setInputEventTimeout(int)}. Like with the
+         * {@link TextField#setTextChangeTimeout(int)}. Like with the
          * {@link #TIMEOUT} mode, an event is forced before
          * {@link ValueChangeEvent}s, even if the user did not keep a pause
          * while entering the text.