[ 
http://www.stripesframework.org/jira/browse/STS-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850#comment-12850
 ] 

Michael Dinsmore commented on STS-792:
--------------------------------------

I think releases with incremental features is better than waiting an 
indeterminate time for some larger set of features.  Seeing how this patch was 
made available over two years ago and it is still not available is a clear 
example driving my point home.  Would I like other HTML5 features?  Sure, but I 
also know I could simplify things *today* if I at least had some of the 
features, like placeholder.

> Add Support for the HTML5 placeholder Attribute to Stripes Input Field Custom 
> Tags
> ----------------------------------------------------------------------------------
>
>                 Key: STS-792
>                 URL: http://www.stripesframework.org/jira/browse/STS-792
>             Project: Stripes
>          Issue Type: Improvement
>          Components: Tag Library
>    Affects Versions: Release 1.5.5
>            Reporter: Walter Rumsby
>            Priority: Minor
>              Labels: html5
>         Attachments: stripes-input-placeholder-patch.txt, 
> stripes-input-placeholder-patch.txt, stripes-input-placeholder-patch.txt
>
>
> One of the new feature of HTML5 is the placeholder attribute for input 
> fields. The placeholder text is displayed in the input field as a hint 
> intended to aid user entry, e.g.
>     <input type="text" name="search-text" placeholder="Enter terms here">
> will display "Enter terms here" if the element has no value in browsers that 
> support the placeholder attribute. For browsers that don't support the 
> attribute, it's possible to use JavaScript to display a placeholder, or a 
> valid approach might be that providing no hint is a valid graceful 
> degradation strategy for older browsers.
> My personal opinion is that there is very little risk using this new 
> attribute (which seems to be the consensus among people advocating HTML5, 
> i.e. there are parts of HTML5 that advocates generally recommend not using 
> until the specification or design of the feature improves).
> While placeholder makes most obvious sense on input type="text", input 
> type="password" and textarea elements the working draft suggests it is valid 
> for all input elements and the textarea element (Chrome, for instance, will 
> not do anything visually if you add a placeholder to a radio button).
> I've attached a patch that should provide support for this attribute when 
> using Stripes' custom tags for input fields (e.g. <stripes:text/>, etc.).
> More information:
> http://www.w3.org/TR/html5/common-input-element-attributes.html#the-placeholder-attribute
> http://www.w3.org/TR/html5/index.html#attributes-1
> http://diveintohtml5.org/forms.html#placeholder
> http://robertnyman.com/2010/06/17/adding-html5-placeholder-attribute-support-through-progressive-enhancement/

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
and much more. Keep your Java skills current with LearnJavaNow -
200+ hours of step-by-step video tutorials by Java experts.
SALE $49.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122612 
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development

Reply via email to