, at 11:11 AM, Chris Bateman chrisb...@gmail.com wrote:
Ugh, I forgot about that. Without subclassing - terseness is a very
minor drawback, but remapping the interface is a big pain.
Could you give us a concrete use case in which remapping the interface is
necessary or hard/impossible to do
needs to be
postponed.
Chris
On Wed, Feb 4, 2015 at 10:51 AM, Ryosuke Niwa rn...@apple.com wrote:
See https://lists.w3.org/Archives/Public/public-webapps/2015JanMar/0435.html
https://lists.w3.org/Archives/Public/public-webapps/2015JanMar/0435.html
first.
On Feb 4, 2015, at 6:43 AM, Chris
at 10:36 AM, Ryosuke Niwa rn...@apple.com wrote:
On Feb 4, 2015, at 10:12 AM, Brian Kardell bkard...@gmail.com wrote:
On Wed, Feb 4, 2015 at 12:41 PM, Chris Bateman chrisb...@gmail.com
wrote:
Yeah, I had noted in that post that wrapping a native element with a
custom element was an option
Niwa rn...@apple.com wrote:
On Feb 3, 2015, at 7:13 AM, Chris Bateman chrisb...@gmail.com wrote:
Why don't we just make all input elements support these new attributes
we're adding?
In my opinion, I'd say because you can't possibly cover every case - what
about doing the same kind
elements - so it might be handy to have custom element callbacks to
assist with it.
Chris
On Mon, Feb 2, 2015 at 9:40 PM, Ryosuke Niwa rn...@apple.com wrote:
On Jan 31, 2015, at 10:40 AM, Chris Bateman chrisb...@gmail.com wrote:
The -webkit-appreance CSS is definitely another issue, so here's
