This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/struts-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 1ac445b Automatic Site Publish by Buildbot
1ac445b is described below
commit 1ac445b74a0e790c78dd0ef997db70733a68b1d7
Author: buildbot <[email protected]>
AuthorDate: Fri Nov 5 10:25:12 2021 +0000
Automatic Site Publish by Buildbot
---
output/tag-developers/form-tags.html | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/output/tag-developers/form-tags.html
b/output/tag-developers/form-tags.html
index c4aa9cb..099517e 100644
--- a/output/tag-developers/form-tags.html
+++ b/output/tag-developers/form-tags.html
@@ -143,7 +143,7 @@
<p>Please make sure you have read the <a href="tag-syntax">Tag Syntax</a>
document and understand how tag attribute syntax works.</p>
<p>Within the form tags, there are two classes of tags: the form tag itself,
and all other tags, which make up
-the individual form elements. The behavior of the form tag is different than
the elements enclosed within it.</p>
+the individual form elements. The behavior of the form tag is different from
the elements enclosed within it.</p>
<h2 id="form-tag-themes">Form Tag Themes</h2>
@@ -197,7 +197,7 @@ the form’s ID can be found by calling <code
class="highlighter-rouge">${parame
<h2 id="template-related-attributes">Template-Related Attributes</h2>
-<table border="1" summary="">
+<table style="border: black 1px solid">
<thead>
<tr>
<td>Attribute</td>
@@ -245,7 +245,7 @@ the form’s ID can be found by calling <code
class="highlighter-rouge">${parame
<h2 id="javascript-related-attributes">Javascript-Related Attributes</h2>
-<table border="1" summary="">
+<table style="border: black 1px solid">
<thead>
<tr>
<td>Attribute</td>
@@ -338,7 +338,7 @@ the form’s ID can be found by calling <code
class="highlighter-rouge">${parame
<h2 id="tooltip-related-attributes">Tooltip Related Attributes</h2>
-<table border="1" summary="">
+<table style="border: black 1px solid">
<tr>
<td>Attribute</td>
<td>Data Type</td>
@@ -366,7 +366,7 @@ the form’s ID can be found by calling <code
class="highlighter-rouge">${parame
<td>tooltipDelay</td>
<td>String</td>
<td>500</td>
- <td>Tooltip shows up after the specified timeout (miliseconds). A
behavior similar to that of OS based tooltips.</td>
+ <td>Tooltip shows up after the specified timeout (milliseconds). A
behavior similar to that of OS based tooltips.</td>
</tr>
<tr>
<td>key</td>
@@ -378,7 +378,7 @@ the form’s ID can be found by calling <code
class="highlighter-rouge">${parame
## General Attributes
-<table border="1" summary="">
+<table style="border: black 1px solid">
<thead>
<tr>
<td>Attribute</td>
@@ -483,10 +483,10 @@ the form’s ID can be found by calling <code
class="highlighter-rouge">${parame
In many of the tags (except for the form tag) there is a unique relationship
between the `name` and `value` attributes.
The `name` attribute provides the name for the tag, which in turn is used as
the control attribute when the form
is submitted. The value submitted is bound to the `name`. In most cases, the
`name` maps to a simple JavaBean property,
-such as "postalCode". On a submit, the value would be set to the property by
calling the `setPostalCode` mutator.
+such as "postalCode". On submit, the value would be set to the property by
calling the `setPostalCode` mutator.
-Likewise, a form control could be populated by calling a JavaBean accessor,
like `getPostalCode`. In the expression l
-anguage, we can refer to the JavaBean property by name. An expression like
"%{postalCode}" would in turn call `getPostalCode`.
+Likewise, a form control could be populated by calling a JavaBean accessor,
like `getPostalCode`. In the expression
+language, we can refer to the JavaBean property by name. An expression like
"%{postalCode}" would in turn call `getPostalCode`.
```ftl
<@s.form action="updateAddress">
@@ -532,7 +532,7 @@ and a validator is associated with that particular field.
> **NOTE**: tooltipConfig is deprecated, use individual tooltip
configuration attributes instead
-Every Form UI component (in xhtml / css_xhtml or any other that extends them)
can have tooltips assigned to them.
+Every Form UI component (in `xhtml` / `css_xhtml` or any other which extends
them) can have tooltips assigned to them.
The Form component's tooltip related attribute, once defined, will be applied
to all form UI components that are created
under it unless explicitly overridden by having the Form UI component itself
defined with their own tooltip attribute.
