[
https://issues.apache.org/jira/browse/SLING-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712984#action_12712984
]
Alexander Klimetschek commented on SLING-649:
---------------------------------------------
> Please note, though, that the value atribute is technically required for
> type="checkbox" inputs by the HTML 4.0.1 spec [1]
The Post servlet should definitely handle both "on" and "true" cases. In
network programming, one should be strict when sending out data, but on the
other hand be very loose in accepting data from others, even if it is not
following the spec. And HTML is the most loosely followed spec anyway (just
look at what browsers accept) ;-)
> checkboxes not handled by SlingPostServlet
> ------------------------------------------
>
> Key: SLING-649
> URL: https://issues.apache.org/jira/browse/SLING-649
> Project: Sling
> Issue Type: Improvement
> Components: Servlets Post
> Environment: Ubuntu AMD64 FF3
> Reporter: Renaud Richardet
> Priority: Minor
>
> I am trying to use checkboxes with the SlingPostServlet, as described in
> http://incubator.apache.org/sling/site/manipulating-content-the-slingpostservlet.html
> <form method="POST" action="/content/page/first">
> <input type="text" name="width" />
> <input type="hidden" name="wi...@typehint" value="Long" />
> <input type="checkbox" name="checked" />
> <input type="hidden" name="chec...@typehint" value="Boolean" />
> ...
> <input type="Submit" />
> </form>
> All elements work fine, excepte the checkbox: the "checked" node property is
> always set to false in JCR after a POST. Can anyone confirm?
> I guess it's because the POST request parameters are:
> width 1234
> wi...@typehint Long
> checked on
> chec...@typehint Boolean
> So, the passed checkbox parameter is "on" instead of "true"
> I guess I would have to modify SlingPropertyValueHandler.setPropertyAsIs() to
> handle "on" values as "true" if @TypeHint is Boolean. Similar to how dates
> values are handled if @TypeHint = date.
> If it's the right way to go, I will create a patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
