henrikerola / expandingtextarea Goto Github PK

It would be handy to have those values settable to 1

com.vaadin.terminal.gwt.server.AbstractCommunicationManager handleVariableBurst
WARNING: Warning: Ignoring variable change for non-existent component, VAR_PID=***

Using vaadin 6.8.4
expanding - 0.1

This component causing error in my app. Widgeset is compiled.
This error fired when i removing component.
In my app i am using navigator7 addon so i have several pages.
When i move from one page to another and focus expanding component and then moving back i get this error. Before each page init i fire remoAllComponents from it. When i am using native textarea there is no problem.

Only the default constructor calls registerRpc(rpc);. Of course every constructor in ExpandingTextArea should contain that line.

Reported here: https://vaadin.com/forum/#!/thread/106199/10442464

If you enter more than just one or two lines into ExpandingTextArea you can see a scrollbar before a new line get added. After some investigation I found out that the scrollbar should never be visible due to its CSS setting (expandingtextarea.css). The reason why the scrollbar appears lies in Vaadin: The primary styleclass is overwritten deeply within AbstractComponentConnector#updateWidgetStyleNames. (At least in Vaadin 7.1.8.) Thus, the styled name ("v-expandingtextarea") set in the ExpandingTextArea constructor does not appear in the HTML-code. (You can check with e.g. FireBug.)

This glitch can easily be fixed in the constructor of ExpandingTextAreaWidget:
public ExpandingTextAreaWidget()
{
// Does not work since TextAreaState has a primary name which has precedence!
// (see AbstractComponentConnector.updateWidgetStyleNames)
// setStyleName(CLASSNAME);
// Adding is only OK if primary style is different to added style:
addStyleName(CLASSNAME);
}

Do mind that this does only work if CLASSNAME is completely different to its primary name which is "v-textarea".

Tested with expandingtextarea-1.0.1 and Vaadin 7.1.8.

Hi,

after including this addon I get this log message on first application access.

2015-10-24 23:47:13.711 INFO  com.vaadin.server.VaadinServlet - Requested resource [/VAADIN/widgetsets/MyWidgetset/expandingtextarea/expandingtextarea.css] not found from filesystem or through class loader. Add widgetset and/or theme JAR to your classpath or add files to WebContent/VAADIN folder.

As a workaround I manually created the folder and copy the css from the jar to the required file.

I think - but I'm not sure - if you move the "expandingtextarea/expandingtextarea.css" in a new folder "public/expandingtextarea/expandingtextarea.css" no further manual action would be required. The folder "public" must be in the same folder as "ExpandingtextareaWidgetset.gwt.xml".

Btw. I'm using Vaadin 7.5.8 and build or compile the widget set with Gradle (https://github.com/johndevs/gradle-vaadin-plugin)

Thanks & BR,
Michael

If you set the TextArea disabled before the initial paint, the client sends an unnecessary RPC call to the server which causes a warning to be printed on the console.

Can you update this so it is compatible with 7, using Vaadin 8?

Hi Hendri,

Just to inform you, we are using this addons from past 6 months in a project. Recently noticed a strange bug which have not a fix pattern but occurs many of the times in same pattern which looks loss of typed/copied text.

Here are the system details:
Java: 1.6.0-45
Tomcat: 7.0.33
Vaadin: 7.6.8
ExpandingTextArea: 1.2.0
Chrome browser: 54 and above

Steps to reproduce:

1. Type some text in text area
2. Move focus away from text area (some times in few other applications)
3. Start typing again in text area and press Enter

=>The latest typed text will be lost.

Could you please help out with this and provide any fix for this or can confirm if it is a BUG in current version.
Would also appreciate if you can provide any Hints to fix at my end as well.

if textarea has a height set and the setValue() contains enough text to wrap in the textarea onload, the component crashes the browser.

textarea {
height:50px;
}

ExpandingTestArea should override any inline/css.