中国福文化网 福文化|福字|福|请福|送福|得福|造福50% off yearly subscriptions, for a limited time!
AdvertisementHow to Build Cross-Browser HTML5 FormsAdvertisementIn this tutorial, we're going to take a look at how to serve HTML5 forms to modern browsers, while compensating for older browsers by using a mix of , ,
and assorted jQuery Plugins.
Introduction
HTML5 powered forms provide a great deal of semantic markup, and remove the need for a lot of JavaScript.
One of the first efforts toward HTML5 was WHATWG's Web Forms 2.0, originally called XForms Basic. The spec introduced new form controls and validation, among other things. Later, it got incorporated into HTML5, and was subsequently stripped of the repetition model, resulting in what we know today as HTML5 Forms.
The ever-present issue, backward compatibility, still remains a headache though, unfortunately. Developers have to deal with the dreaded Internet Explorer, which, as you might have guessed, doesn't provide much support for the latest advancement in forms - even in the latest available beta of IE9. Older versions of IE? Fagetaboutit.
Nonetheless, we want to use these new features, and use them, we will! Today, we're going to look at some of these new elements. We'll check whether the browser support these features, and if not, provide fallbacks using CSS and JavaScript.
Tool: Modernizer
We'll be providing fallbacks only to browsers that don't support HTML5 forms, or certain parts of them. But instead of relying on browser sniffing, the proper technique is to use feature detection. We'll use the popular
Modernizr is a small JavaScript library that tests the current browser against a plethora of HTML5 and CSS3 features.
If you want to learn more about Modernizr, you might check out
premium tutorial available on the Tuts+ Marketplace.
Tool: Webforms2
is a JavaScript library by , which provides a cross-browser implementation of the "previous" version of HTML5 forms, the "WHATWG Web Forms 2.0" specification.
We'll be using it for validation and extending functionality for current elements.
&script type="text/javascript" src="webforms2/webforms2-p.js"&&/script&
Widget: Slider
The spec describes the range input as an imprecise control for setting the element's value to a string representing a number.
&input type="range" name="slider"&
Here's a preview of how it looks in Opera 10.63:
To provide fallback for other browsers,
we'll use jQuery UI's slider widget.
First, we create our initializing function, which creates the slider from the input range element.
var initSlider = function() {
$('input[type=range]').each(function() {
var $input = $(this);
var $slider = $('&div id="' + $input.attr('id') + '" class="' + $input.attr('class') + '"&&/div&');
var step = $input.attr('step');
$input.after($slider).hide();
$slider.slider({
min: $input.attr('min'),
max: $input.attr('max'),
step: $input.attr('step'),
change: function(e, ui) {
$(this).val(ui.value);
We create a new &div& element for each of our range inputs, and call the slider on that node. This is because
jQuery UI's slider will not work by calling it directly on the input element.
Note that we're getting attributes from the input, such as min, max and step,, and are then using them as parameters for the slider. This helps our fallback slider mimic the real HTML5 slider in functionality.
Next, we'll use Modernizr to determine if the current browser supports this input type. Modernizr adds classes to the document element (html), allowing you to target specific browser functionality in your stylesheet. It also creates a self-titled global JavaScript object which contains properties for each feature: if a browser supports it, the property will evaluate to true and if not, it will be false.
With that knowledge, to detect support for input types, we'll use Modernizr.inputtypes[type].
if( !Modernizr.inputtypes.range ){
$(document).ready( initSlider );
If there's no support for the range input, we attach the initSlider function to jQuery's document.ready, to initialize our function after the page has loaded.
This is how the slider should look in a browser without native support for the range input.
Widget: Numeric Spinner
To quote :
Asking for a number is trickier than asking for an email address or web address.
That's why we're provided with a separate form control which specifically deals with numbers: the numeric spinner, also called the numeric stepper.
&input type="number" value="2"&
At the time of this writing, it is supported by Opera and Webkit- here's a snapshot from Opera 10.6.
Because jQuery doesn't provide a numeric spinner, we'll instead use a jQuery plugin by , built as a jQuery UI widget.
We implement the same build out the function to create the spinner, test with Modernizr, and attach the function to $(document).ready.
var initSpinner = function() {
$('input[type=number]').each(function() {
var $input = $(this);
$input.spinner({
min: $input.attr('min'),
max: $input.attr('max'),
step: $input.attr('step')
if(!Modernizr.inputtypes.number){
$(document).ready(initSpinner);
Because number inputs also support min, max and step, we get the attributes from the field, and use them as parameters for initializing the numeric spinner plugin.
And our fallback widget looks like so:
Widget: Date Picker
There are no less than six input types to serve as date pickers.
datetime and
and datetime-local
At the time of this writing, the only browser that properly supports them is Opera, versions 9+.
&input type="date"&
&input type="month"&
&input type="week"&
&input type="time"&
&input type="datetime"&
&input type="datetime-local"&
For now, we'll only provide fallback for the date input, using the jQuery UI Datepicker. Feel free to use any other plugin to completely mimic the functionality of the HTML5 date picker input in your implementation.
var initDatepicker = function() {
$('input[type=date]').each(function() {
var $input = $(this);
$input.datepicker({
minDate: $input.attr('min'),
maxDate: $input.attr('max'),
dateFormat: 'yy-mm-dd'
if(!Modernizr.inputtypes.date){
$(document).ready(initDatepicker);
Widget: Color Picker
Right now, no browser provides support for the color input. So, until they catch up, they'll all need to use our fallback technique.
&input type="color"&
We'll use 's
jQuery plugin, since jQuery UI does not provide one with the base pack yet.
var initColorpicker = function() {
$('input[type=color]').each(function() {
var $input = $(this);
$input.ColorPicker({
onSubmit: function(hsb, hex, rgb, el) {
$(el).val(hex);
$(el).ColorPickerHide();
if(!Modernizr.inputtypes.color){
$(document).ready(initColorpicker);
And our result:
Input Type: Search
The new search input type is implicitly used for semantics, but could provide a lot of interesting functionalities in the future.
&input type="search"&
Currently, only Webkit-based browsers offer support for this feature. The spec also supports a results attribute to display a number of searched terms in a dropdown.
It should look like this on Safari on OS X:
The rest of the browsers display this as a standard text field, so you may confidently use it with the standard markup.
Input Type : URL and Email
These two input types, url and email, are used for validation purposes. They can be particularly useful in mobile browsers, where the on-screen keyboard layout can be changed to suit the focused field. This is already implemented in Safari on iOS(iPhone, iPad, iPod), and some versions of Android.
&input type="email"&
&input type="url"&
These input types can be implemented by Webforms2 in other browsers.
You can freely use these types in your new projects, as they fallback to simple textboxes. On your phone, you'll find that the keyboard changes accordingly, if you supply these types to your inputs.
Attribute: Required Fields
The new spec introduces the very handy required attribute. Instead of
using fancy JavaScript to take care of our required fields, now we can easily use this attribute.
&input type="email" required&
For browsers that don't support this attribute,
we can again use Webforms2. So, since we've included it from the start, there's nothing to worry about.
Note: Be sure to assign a name attribute to your form elements, or the required attribute will not take effect.
Attribute: Pattern
The pattern attribute is used for field validation and accepts values only if they match a specific format, defined with . If the entered value does not match the pattern, the form won't submit.
For example, to validate a phone number, we'd have to use the following pattern, or regular expression:
&input type="text" name="Tel" pattern="^0[1-689][0-9]{8}$"&
The pattern attribute can be implemented in browsers that don't support it, by using
Webforms2.
Attribute: Autofocus
The autofocus attribute does just what it says:
automatically focuses one of our controls. It is currently supported in Webkit-based browsers(Safari, Chrome, etc.) and Opera. Remember: only one form control can receive this attribute.
&input type="email" autofocus&
Webforms2 takes care of the implementation in unsupported browsers.
Attribute: Placeholder
The placeholder attribute is something we've been doing with JavaScript for years. It adds a piece of information about the field, like a short description, that disappears when the field is focused.
&input name="name" placeholder="First Name"&
This attribute is supported by the latest Beta Firefox and Webkit browsers.
To mimic the behavior in older browsers, we'll use the
jQuery plugin, by .
var initPlaceholder = function() {
$('input[placeholder]').placehold();
if(!Modernizr.input.placeholder){
$(document).ready(initPlaceholder);
Attribute: Min, Max and Step
The min, max and step input attributes specify constraints for certain form controls, such as the date picker, number, and range. You can surely guess the purpose of min and max from their names. The step attribute specifies the multiple range for each click, or "step." For isntance, if the step value is 2, the accepted values could be 0, 2, 4, and so on.
&input type="range" name="slider" min="0" max="20" step="5" value="0"&
These attributes are only supported by Opera and Webkit browsers right now, and are implemented, as fallback for other browsers, by Webforms2.
Conclusion
We've learned today that creating forms and providing fallback for most of the new additions is a fairly easy task. If people are still trying to scare you from using HTML5 today, pay
start using the awesome tools you have at your disposal right now!
Be sure to also check out 's great , which provide similar solutions, with native JavaScript widgets.
Further Reading
Advertisement
just $90/yr AdvertisementEnvato Tuts+ tutorials are translated into other languages by our community members&you can be involved too!Powered byAdvertisementcourse now
has a range of items for sale to help get you started.,亚洲城ca88 - 亚洲城在线娱乐城
江西昌赣客专铁路最大规模轨道板场正式投产新丝路资讯网讯(记者 常魁星 通讯员王雪莲
上海嘉闵高架桥2-6标上“两学一做”专题党课新丝路资讯网讯（记者 常魁星 通讯员 陈敏
图览资讯－天下原创
　　　　　　　　　　　　互联网只是渠道，内容营销为王！高速新媒体网　/专注于原创、速度、策略！
常魁星_中国铁路、高速亚洲城ca88报道集
江西昌赣客专铁路最大规模轨道板场正式投产新丝路资讯网讯(记者 常魁星 通讯员王雪莲
企业亚洲城ca88
浙江亚洲城ca88
高速新媒体网－文化社区－图库
新媒体品牌链接这是商业链接。
合作媒体媒体手拉手，全国新媒体抱团推进中国梦！
义务链接传递正能量，践行中国梦。LLDB Homepage
The LLDB Debugger
LLDB is a next generation, high-performance debugger. It is built as a set
of reusable components which highly leverage existing libraries in the
larger LLVM Project, such as the Clang expression parser and LLVM
disassembler.
LLDB is the default debugger in Xcode on Mac OS X and supports
debugging C, Objective-C and C++ on the desktop and iOS devices and simulator.
All of the code in the LLDB project is available under the standard
, an open source "BSD-style" license.
In order to achieve our goals we decided to start with a fresh architecture
that would support modern multi-threaded programs, handle debugging symbols
in an efficient manner, use compiler based code knowledge and have plug-in
support for functionality and extensions. Additionally we want the debugger
capabilities to be available to other analysis tools, be they scripts or
compiled programs, without requiring them to be GPL.
LLDB currently converts debug information into clang types so that
it can leverage the clang compiler infrastructure.
This allows LLDB to support the latest C, C++, Objective C and Objective C++
language features and runtimes in expressions without having to reimplement any
of this functionality. It also leverages the compiler to take care of all ABI
details when making functions calls for expressions, when disassembling
instructions and extracting instruction details, and much more.
The major benefits include:
Up to date language support for C, C++, Objective C
Multi-line expressions that can declare local variables and types
Utilize the JIT for expressions when supported
Evaluate expression Intermediate Representation (IR) when JIT can't be used
The LLDB debugger APIs are exposed as a C++ object oriented interface in a shared library.
The lldb command line tool links to, and uses this public API. On Mac OS X the shared library
is exposed as a framework named LLDB.framework, and unix systems expose it as lldb.so.
The entire API is also then exposed through Python script bindings which allow the API to be used
within the LLDB embedded script interpreter, and also in any python script that loads the lldb.py
module in standard python script files. See the
page for more details on how
and where Python can be used with the LLDB API.
Sharing the LLDB API allows LLDB to not only be used for debugging, but also for symbolication,
disassembly, object and symbol file introspection, and much more.
LLDB is known to work on the following platforms, but ports to new
platforms are welcome:
Mac OS X desktop user space debugging for i386 and x86-64
iOS simulator debugging on i386
iOS device debugging on ARM
Linux local user-space debugging for i386 and x86-64
FreeBSD local user-space debugging for i386 and x86-64
Windows local user-space debugging for i386 (*)
(*) Support for Windows is under active development.
Basic functionality
is expected to work, with functionality improving rapidly.
To check out the code, use:
svn co http://llvm.org/svn/llvm-project/lldb/trunk lldb
Note that LLDB generally builds from top-of-trunk
On Mac OS X with Xcode
On Linux and FreeBSD (with clang and libstdc++/libc++)
On NetBSD (with GCC and clang and libstdc++/libc++)
On Windows with VS 2012 or higher using CMake
for platform-specific build instructions.
Discussions about LLDB should go to the
Commit messages for the lldb SVN module are automatically sent to the
mailing list, and this is also the preferred mailing list for patch
submissions.永利娱乐,澳门新葡京官网 - 澳门新濠天地官网
后使用澳门新葡京官网没有帐号？
<img src="/mylogo.png" height='75' width='121' alt="永利娱乐" alt="澳门新葡京官网" border="0" />
只需一步，快速开始
扫一扫，访问微永利娱乐
2015宁波质量人交流会邀请函[宁波]2014年澳门新葡京官网宁波质量人交流会-报名贴[你最喜欢什么时候刷微信呢？澳门新葡京官网公众平台，你写永利娱乐我来分享活动九峰山的杨梅熟了，来感受下大自然吧！
你永远也不会知道自己有多坚强，当你除了坚强，只剩坚强。
澳门新葡京官网是大家网上交流的免费场所!站内资料完全免费提供给广大网友！但是不劳无获，天经地义！澳门新濠天地官网的金
在你决定申请版主之前，请你确定是否满足以下所有条件：
1、你是否对你所申请的领域有所专长并是自己兴趣
o1wfobdg6q[]
Vivian楚[]
Vivian楚[]
Vivian楚[]
Vivian楚[]
Vivian楚[]
Vivian楚[]
Vivian楚[]
Vivian楚[]
Vivian楚[]
Vivian楚[]
Vivian楚[]
pathbreaker[]
Psaex588[]
最新永利娱乐
这个表格是公司的格式，我就按公司这个格式做了第1次 审核的结果
（附表）日产生产方式中的
现场管理原文的位置及结构图 4
澳门新濠天地官网新帖
（附表）日产生产方式中的
现场管理原文的位置及结构图
推销员与准顾客交谈之前，需要适当的开场白。开场白的好坏，几乎可以决
求职澳门新濠天地官网
澳门新濠天地官网实习审核员 免费挂靠快速攒够经历质量工程师澳门新濠天地官网检验员澳门新濠天地官网上海品尊能源科技有限公司澳门新濠天地官网质量工程师中清能绿洲科技股份有限公司澳门新濠天地官网质量工程师衢州市意美旭光伏科技有限公司澳门新濠天地官网生产质量江苏爱康科技股份有限公司澳门新濠天地官网质量工程师
文件共分：
1.办公室员工岗位考核评价表
2.办公室员工绩效评价表
澳门新濠天地官网
2013年7月至8月全国“国家注册审核员”培训招生通知
一、培训对象具有
Powered by