S. Pieper created WICKET-5498:
---------------------------------
Summary: OutputComponentPath Html5 compliance
Key: WICKET-5498
URL: https://issues.apache.org/jira/browse/WICKET-5498
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 6.11.0
Environment: Jetty, Windows7, IE, Firefox
Reporter: S. Pieper
Priority: Minor
This issue has cropped up in our project because the attribute name
"wicket-path" or "wicketpath" is not compliant with html5.
Custom attributes need to start with "data" as in "data-wicket-path"
http://www.w3.org/TR/2010/WD-html5-20101019/elements.html#embedding-custom-non-visible-data-with-the-data-attributes
It would be appreciated if this could be made configurable. It is possible to
write a custom implementation of the DebugSettings interface, however, the
problem lies in the Component class, where currently the string wicketpath is
hardcoded.
If Component could be adapted like this:
{{protected void onComponentTag(final ComponentTag tag)}}
...
{{tag.put(getApplication().getDebugSettings().getOutputComponentPath() ,
path);}}
IDebugSettings would need two new methods:
{{String getOutputComponentPath();}}
{{setOutputComponentPath(boolean enabled,String outputComponentPath);}}
And the implementation of IDebugSettings in the class DebugSettings would of
course have to implement these methods and store the outputComponentpath in a
field.
This would make it possible to use wicketpath and be html5 compliant.
This has already been referred to in
https://issues.apache.org/jira/browse/WICKET-1877
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
