OLD | NEW |
---|---|
(Empty) | |
1 <link rel="import" href="chrome://resources/polymer/polymer/polymer.html"> | |
2 <link rel="import" | |
3 href="chrome://resources/polymer/paper-input/paper-input-decorator.html"> | |
4 <link rel="import" href="chrome://resources/polymer/core-input/core-input.html"> | |
5 <link rel="import" href="chrome://resources/cr_elements/cr_events/cr_events.html "> | |
michaelpg
2015/02/13 00:08:29
nit: let's be consistent in wrapping
Jeremy Klein
2015/02/13 00:22:54
Done.
| |
6 | |
7 <polymer-element name="cr-input"> | |
8 <template> | |
9 <link rel="stylesheet" href="cr_input.css"> | |
10 <cr-events id="events"></cr-events> | |
11 | |
12 <paper-input-decorator id="decorator" label="{{label}}" floatingLabel="{{flo atingLabel}}" | |
michaelpg
2015/02/13 00:08:28
nit: 12, 14, 15 should be limited to 80 chars wide
michaelpg
2015/02/13 00:08:29
we use {{ spaces }} inside data-binding braces
Jeremy Klein
2015/02/13 00:22:54
Where did this convention come from? This isn't do
Jeremy Klein
2015/02/13 00:22:55
Waiting on verification about 80-char limit. If we
michaelpg
2015/02/13 05:45:13
Hmm, I guess the truth is *I* use {{ spaces }} ins
michaelpg
2015/02/18 00:17:18
ping on this nit
Jeremy Klein
2015/02/18 01:10:49
Done.
| |
13 value="{{value}}" disabled?="{{disabled}}" error="{{error}}"> | |
14 <input is="core-input" id="input" value="{{value}}" committedValue="{{comm ittedValue}}" | |
15 disabled?="{{disabled}}" required="{{required}}" pattern="{{pattern}}" type="{{type}}"> | |
16 </paper-input-decorator> | |
17 </template> | |
18 <script src="cr_input.js"></script> | |
19 </polymer-element> | |
OLD | NEW |