Make h:outputFormat support outputting to a request scope variable defined by a new var attribute
- Dominant language
- Java
- Stars
- 127
- Forks
- 59
- Avg merge
- 23h
- Merged PRs (30d)
- 7
Description
See the OmniFaces o:outputFormat for examples and description:
[http://showcase.omnifaces.org/components/outputFormat](http://showcase.omnifaces.org/components/outputFormat)
I've used this feature for building formatted text to use on h:commandLink buttons, and also to automatically escape URL parameter values that end up being used in my template when referencing CSS files (path parameters). When the URL parameter values are used without o:outputFormat we're able to execute XSS attacks. It would be really great if this feature were part of the 2.3 spec.
Contributor guide
Research direction
Start by reviewing the linked OmniFaces o:outputFormat examples and description, then compare them with Jakarta Faces h:outputFormat and the relevant specification. Done means defining how a new var attribute stores formatted output in request scope, including the described escaping behavior, and documenting the resulting 2.3 feature.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100