Daniel Fernández
Daniel Fernández
Building on #872, we should consider the allowed classes there a _default_ and move towards an even more restricted scenario in which all classes are forbid for static use (`@SomeClass@`...
(Moved from thymeleaf/thymeleaf-spring#167 by @hamishlawson) --- It would make template code much cleaner if Thymeleaf's Spring dialect handled Java 8 Optionals transparently rather than obliging explicit calls to the likes...
From: http://sourceforge.net/tracker/?func=detail&aid=3495263&group_id=509826&atid=2072662 The Mozilla "Tips for authoring fast-loading HTML pages" recommend that the HTML page is stripped of whitespace before being delivered to the client. https://developer.mozilla.org/en/HTML/Tips_for_authoring_fast-loading_HTML_pages#Reduce_page_weight It would be extremely...
See #578. In cases such as these polymer web components, code like: ```html TAB ONE TAB TWO TAB THREE ``` ...does add new custom components, but being web components their...
Once `th:insert` has been introduced in Thymeleaf 3.0 and documentation for `th:include` has been retired, the latter should be deprecated (with warnings being issued in Thymeleaf 3.1). This `th:include` should...
Separating the template resolution and template processing mechanisms, the first one returning a `Template`, `ResolvedTemplate` or similar, and then the second one performing processing in itself could bring some benefits....
After applying #59 in Thymeleaf 3.0, which meant the deprecation (and issue of warnings) when `execInfo` used as a context variable instead of an expression object, it makes sense that...
In the same way as #425 should make inlining avoid creating new Strings by means of using `StringWriter`s, maybe the same mechanism could be applied to the insertion of fragments...
After introducing fragment expressions in Thymeleaf 3.0 (see #451), the legacy _unwrapped syntax_ for these fragment expressions (i.e. `th:replace` values without `~{...}`) should be marked as _deprecated_ in preparation for...
Once #193 has been implemented in Thymeleaf 3.0, the `#httpServletRequest` and `#httpSession` expression object names should start to issue warnings whenever used in 3.1. These will be removed in 3.2.