AO Taglib Changelog

1. <ao:style> may now be used outside the scope of a StyleAttribute (or with the new forceElement="true" attribute) to manually establish a style context. Under the usual case of being within an XHTML container context, this will result in the expected <style> element.
2. Tags that generate plaintext output, such as the default type on <ao:message>, <ao:out>, and <ao:write>, will have the plaintext content surrounded by "…" and fully encoded as a CSS string.

• <ao:action>
• <ao:href>
• <ao:img>
• <ao:src>
• <ao:url>

1. New "scope" attribute that allows the in-context translator to be disabled only in the tag body.
2. New "mode" attribute that provides the new mode used when disabling the in-context translator.

Reverted a previous change made on 2020-03-01 that was released in version 5.0.0 on 2020-03-27. Encoding of in-context translation lookup markups is required after all.

One example is the lookup IDs added inside alt attributes like alt="<##<value>##>". With this bug, this was incorrectly written as alt="<##<value>##>", which fails XML validation.

This bug is unlikely to affect production systems for two reasons:

1. Lookup markups are only performed when in-context translations are enabled, which is only when in development mode.
2. Most production sites are served in SGML mode, where browsers will handle the incorrect HTML formatting. XML mode is used in development specifically for this stricter validation.

Minimized the duplication in implementation by using default interface methods, abstract base classes, and XML entities.

Added more global attributes:

1. dir
2. Added global attribute data-*, with implementations for both HTML attribute and JavaScript property names.

1. Use the serialization active on the current request.
2. Use the application context-paramcom.aoindustries.encoding.Serialization.default that allows an application to control the selection of HTML versus XHTML.
3. When this context-param is unspecified or auto, determine the serialization based on the client's Accept header.

1. Use the doctype active on the current request.
2. Use the application context-paramcom.aoindustries.encoding.Doctype.default that allows an application to control the default doctype.
3. When this context-param is unspecified or default, defaults to HTML5, which results in a breaking change (this tag used to default to STRICT).

1. *.class
2. *.enctype
3. *.httpEquiv
4. *.id
5. *.itemprop
6. *.name
7. *.rel
8. *.target
9. *.type

1. ${ao:encodeURIComponent()}
2. ${ao:decodeURIComponent()}
3. ${ao:encodeURI()}
4. ${ao:decodeURI()}

1. UrlUtils updated with new canonical parameters.
2. New canonical attribute on:
   • <ao:a>
   • <ao:iframe>
   • <ao:img>
   • <ao:link>
   • <ao:redirect>
   • <ao:script>
3. In auto mode, last modified stamping is not performed on Canonical URLs.

• <ao:a>
• <ao:iframe>
• <ao:img>
• <ao:link>
• <ao:script>

1. Added new usemap and ismap attributes to <ao:img>
2. alt attribute of <ao:img> is now optional when usemap provided.
3. Added new <ao:map> tag
4. Added new <ao:area> tag

1. New src attribute
2. New absolute attribute
3. New canonical attribute
4. New addLastModified attribute
5. New width attribute
6. New height attribute
7. New alt attribute, required for type="image"
8. New title attribute
9. New dynamic attributes param.*

1. This project uses managed dependencies.
2. This project's managed dependencies may also be imported by other projects.

• <encoding:mysql> - must be valid MySQL command "mysql" input
• <encoding:psql> - must be valid PostgreSQL command "psql" input
• <encoding:sh> - must be valid shell script

The lock contention profiler in NetBeans is just showing "java.lang.Object" all over, and can't seem to get from the lock object id to the actual object in the heap dump using OQL (id not found).