Replace setRequired & HasRequired with setRequiredIndicator
Vaadin 7 compatiblity fields still use setRequired via AbstractField (legacy).
Public setRequiredIndicator is added to AbstractField, AbstractMultiSelect and AbstractSingleSelect.
Internally it is still handled on AbstractComponent & -Connector level.
Changes the declarative syntax, required -> required-indicator-visible.
Fixes vaadin/framework8-issue#419
Change-Id: I940dc66944d27584bd78e5452aee627ee3abd03a
All components are now in immediate mode by default.
V7 compatibility components will use AbstractLegacyComponent that has immediate.
V7 ColorPickerPopup will not have setImmediate, since it extends V8 Window,
which is not in V7 compatibility packages.
Removed OutOfSync and ResynchronizeAfterAsyncRemoval Tests,
since those tested UI in not immediate mode, which is invalid now.
Removed WindowResizeListener, LazyWindowResize, test UIs,
since both used immediate and there were no test run for either.
Change-Id: Ie1c8cfa4c48461db944ff9b13efe8473c5a3298f
This patch updates server side add*Listener methods to return
a registration object and deprecates their corresponding
remove*Listener methods.
Additionally this patch removes add/removeListener methods which were
deprecated in 7.0.
Change-Id: I26ac5f11882512288fbbf601c7cb2aaff653ec76
Remove shortcut listener from subclasses of AbstractComponent (#16498).
e.g., Panel shadows actionManager with its own instance field
* solution: always invoke getActionManager()
Change-Id: Ibeca2ad53cb1175ae1ebcfb4d68b3d2bf36ea8b2
Don't clear element content in AbstractComponent.writeDesign (#17488)
WriteDesign now assumes the element it receives is pristine, so elements cannot
be reused without someone else clearing them first. Currently only
DesignContext.createElement directly invokes writeDesign, and it always passes a
new element to it.
Change-Id: Icb777da1d73a28150041914dd9743e7aa0b25e16
Declarative for DateFields (and related) with ISO8601 (#16313)
DesignAttributeHandler supports method names that contains some words in
uppercase
DesignAttributeHandler and other components now use extensible Formatter
with Converters rather than static methods
Change-Id: I9f68414bd4821f47ff37a26375091d154cae9a93
* A root component with @DesignRoot must always use its superclass for
default values. Otherwise the written design will be empty as the
design is read in the constructor.
* A component which is not the root must not write its component tree
if the component tree is generated in the constructor. This is a
simplification which should be good enough for most cases (can't add
children in constructor and also using addComponent - in this case
the component added with addComponent will not be written).
* Test cases for nested templates
Change-Id: I3a384d1d8654b9865a3a790ebeb055a300a62135
Denis
Ilia Motornyi
Leif Åstrand
Per-Åke Minborg
Teemu Suo-Anttila
Pekka Hyvönen
Aleksi Hietanen
Artur Signell
Henri Sara
Johannes Dahlström
Edoardo Vacchi
John Ahlroos
patrik
Miki
Matti Hosio
Mika Murtojarvi