[Bug 12988] New: I'm a bit in trouble on what type to apply for zip- postcodes. I would use type=number, but then I cant use the maxlenght attribute. While using type=text there are no max min attributes. No matter what type I choose, none of them works for zip- postcodes

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12988

           Summary: I'm a bit in trouble on what type to apply for zip-
                    postcodes. I would use type=number, but then I cant
                    use the maxlenght attribute. While using type=text
                    there are no max min attributes. No matter what type I
                    choose, none of them works for zip- postcodes
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#tex
                    t-state-and-search-state
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#text-state-and-search-state
Complete: http://www.whatwg.org/c#text-state-and-search-state

Comment:
I'm a bit in trouble on what type to apply for zip- postcodes. I would use
type=number, but then I cant use the maxlenght attribute. While using
type=text there are no max min attributes. No matter what type I choose, none
of them works for zip- postcodes. I would suggest to add a type=zip to the
specifications.

Posted from: 178.198.193.207
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101
Firefox/4.0.1

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Saturday, 18 June 2011 13:34:03 UTC