This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 244558 - Misleading error message for <input type="number" pattern="">
Summary: Misleading error message for <input type="number" pattern="">
Status: NEW
Alias: None
Product: web
Classification: Unclassified
Component: HTML Editor (show other bugs)
Version: 8.0
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Milutin Kristofic
Depends on:
Reported: 2014-05-17 02:59 UTC by _ gtzabari
Modified: 2015-11-23 10:36 UTC (History)
0 users

See Also:
Exception Reporter: 33.33


Note You need to log in before you can comment on or make changes to this bug.
Description _ gtzabari 2014-05-17 02:59:47 UTC
Product Version: NetBeans IDE 8.0 (Build 201403101706)
Updates: NetBeans IDE is updated to version NetBeans 8.0 Patch 1.1
Java: 1.8.0; Java HotSpot(TM) 64-Bit Server VM 25.0-b70
Runtime: Java(TM) SE Runtime Environment 1.8.0-b132
System: Windows 7 version 6.1 running on amd64; Cp1252; en_CA (nb)
User directory: C:\Users\Gili\AppData\Roaming\NetBeans\8.0
Cache directory: C:\Users\Gili\AppData\Local\NetBeans\Cache\8.0

Netbeans flags "pattern" as an illegal attribute, but according to <input pattern=""> is legal.
Comment 1 _ gtzabari 2014-05-17 03:14:26 UTC
It turns out that Netbeans support <input pattern=""> but the error message is misleading. Given:

  <input id="price" type="number" placeholder="Price" pattern="^\\$?(([1-9](\\d*|\\d{0,2}(,\\d{3})*))|0)(\\.\\d{1,2})?$">

Netbeans warns:

  Attribute "pattern" not allowed on element "input" at this point.

Expected behavior: The warning should explain that attribute "pattern" is not allowed because attribute "type" is already present.
Comment 2 AndreasBuck 2015-05-26 00:34:43 UTC
My understanding is that both tags should be allowed together. Or even are necessary to be together:
"Note: The pattern attribute works with the following input types: text, search, url, tel, email, and password"
As additional types can be defined, the error might just be too restrictively looking for a combination of "pattern" with one of the listed types. Which does not include "number".