Replace use of the <tt> HTML tag in Javadoc
The <tt> HTML tag was used in HTML 4 to define teletype text. It is not supported in HTML5, and its use is discouraged. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/tt Closes gh-28819
This commit is contained in:
@@ -628,17 +628,17 @@ public abstract class WebUtils {
|
||||
* following algorithm:
|
||||
* <ol>
|
||||
* <li>Try to get the parameter value using just the given <i>logical</i> name.
|
||||
* This handles parameters of the form <tt>logicalName = value</tt>. For normal
|
||||
* This handles parameters of the form {@code logicalName = value}. For normal
|
||||
* parameters, e.g. submitted using a hidden HTML form field, this will return
|
||||
* the requested value.</li>
|
||||
* <li>Try to obtain the parameter value from the parameter name, where the
|
||||
* parameter name in the request is of the form <tt>logicalName_value = xyz</tt>
|
||||
* parameter name in the request is of the form {@code logicalName_value = xyz}
|
||||
* with "_" being the configured delimiter. This deals with parameter values
|
||||
* submitted using an HTML form submit button.</li>
|
||||
* <li>If the value obtained in the previous step has a ".x" or ".y" suffix,
|
||||
* remove that. This handles cases where the value was submitted using an
|
||||
* HTML form image button. In this case the parameter in the request would
|
||||
* actually be of the form <tt>logicalName_value.x = 123</tt>. </li>
|
||||
* actually be of the form {@code logicalName_value.x = 123}.</li>
|
||||
* </ol>
|
||||
* @param parameters the available parameter map
|
||||
* @param name the <i>logical</i> name of the request parameter
|
||||
|
||||
@@ -192,8 +192,8 @@ class InternalPathPatternParser {
|
||||
* Just hit a ':' and want to jump over the regex specification for this
|
||||
* variable. pos will be pointing at the ':', we want to skip until the }.
|
||||
* <p>
|
||||
* Nested {...} pairs don't have to be escaped: <tt>/abc/{var:x{1,2}}/def</tt>
|
||||
* <p>An escaped } will not be treated as the end of the regex: <tt>/abc/{var:x\\{y:}/def</tt>
|
||||
* Nested {...} pairs don't have to be escaped: <code>/abc/{var:x{1,2}}/def</code>
|
||||
* <p>An escaped } will not be treated as the end of the regex: <code>/abc/{var:x\\{y:}/def</code>
|
||||
* <p>A separator that should not indicate the end of the regex can be escaped:
|
||||
*/
|
||||
private void skipCaptureRegex() {
|
||||
|
||||
@@ -26,7 +26,7 @@ import org.springframework.web.util.pattern.PathPattern.MatchingContext;
|
||||
|
||||
/**
|
||||
* A regex path element. Used to represent any complicated element of the path.
|
||||
* For example in '<tt>/foo/*_*/*_{foobar}</tt>' both <tt>*_*</tt> and <tt>*_{foobar}</tt>
|
||||
* For example in '<code>/foo/*_*/*_{foobar}</code>' both {@code *_*} and {@code *_{foobar}}
|
||||
* are {@link RegexPathElement} path elements. Derived from the general
|
||||
* {@link org.springframework.util.AntPathMatcher} approach.
|
||||
*
|
||||
|
||||
Reference in New Issue
Block a user