HTMLConstructor implementation

Implemented HTMLConstructor extended attribute.

Specs: https://html.spec.whatwg.org/#html-element-constructors

Replaced V8HTMLElementCustom with V8HTMLConstructor

Add new extended attribute [HTMLConstructor] to bindings and IDLExtendedAttributes.txt
  Added description to IDLExtendedAttributes.md and re-organized descriptions
  Added checks for conflicting extended attributes with [HTMLConstructor] in v8_interface.py
  Edited jinja templates for [HTMLConstructor] interface

Replaced [CustomConstructor] with [HTMLConstructor] in HTMLElement.idl

BUG=648828
Committed: https://crrev.com/6ad512924f794cd4cbee80246106716993919bde
Cr-Commit-Position: refs/heads/master@{#423068}

[yurak, 2016-10-03 05:07:47]

Description was changed from

==========
HTMLConstructor implementation WIP

BUG=
==========

to

==========
https://html.spec.whatwg.org/#html-element-constructors

Replaced V8HTMLElementCustom with V8HTMLConstructor

Add new extended attribute [HTMLConstructor] to bindings and
IDLExtendedAttributes.txt
  Added description to IDLExtendedAttributes.md and re-organized descriptions
  Added checks for conflicting extended attributes with [HTMLConstructor] in
v8_interface.py
  Edited jinja templates for [HTMLConstructor] objects

Added [HTMLConstructor] to HTMLElement.idl

BUG=648828
==========

[yurak, 2016-10-03 05:12:13]

Description was changed from

==========
https://html.spec.whatwg.org/#html-element-constructors

Replaced V8HTMLElementCustom with V8HTMLConstructor

Add new extended attribute [HTMLConstructor] to bindings and
IDLExtendedAttributes.txt
  Added description to IDLExtendedAttributes.md and re-organized descriptions
  Added checks for conflicting extended attributes with [HTMLConstructor] in
v8_interface.py
  Edited jinja templates for [HTMLConstructor] objects

Added [HTMLConstructor] to HTMLElement.idl

BUG=648828
==========

to

==========
The HTMLConstructor allows "new HTMLElement()" to be called from the console.
Specs: https://html.spec.whatwg.org/#html-element-constructors

Replaced V8HTMLElementCustom with V8HTMLConstructor

Add new extended attribute [HTMLConstructor] to bindings and
IDLExtendedAttributes.txt
  Added description to IDLExtendedAttributes.md and re-organized descriptions
  Added checks for conflicting extended attributes with [HTMLConstructor] in
v8_interface.py
  Edited jinja templates for [HTMLConstructor] interface

Replaced [CustomConstructor] with [HTMLConstructor] in HTMLElement.idl


LayoutTests for custom-elements run correctly with these changes.

BUG=648828
==========

[yurak, 2016-10-03 05:14:42]

yurak@google.com changed reviewers:
+ dominicc@chromium.org

[yurak, 2016-10-03 05:15:13]

yurak@google.com changed reviewers:
+ haraken@chromium.org

[dominicc (has gone to gerrit), 2016-10-03 05:48:06]

The CQ bit was checked by dominicc@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-03 05:48:18]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[dominicc (has gone to gerrit), 2016-10-03 05:50:26]

core/html LGTM.

haraken--could you take a look for bindings?

yurak is working at this piece by piece. First step is to move the custom
HTMLElement constructor where we can reuse it; next step will be to generalize
it to work with other HTML*Element types and start by applying it to one other
element, eg HTMLDivElement. Then roll it out to all elements.

https://codereview.chromium.org/2385073002/diff/1/third_party/WebKit/Source/b...
File third_party/WebKit/Source/bindings/IDLExtendedAttributes.md (right):

https://codereview.chromium.org/2385073002/diff/1/third_party/WebKit/Source/b...
third_party/WebKit/Source/bindings/IDLExtendedAttributes.md:307: Usage: Must
take no arguments, and must not appear on amything other than an interface. It
much appear once on an interface, and the interface cannot be annotated with
`[Constructor]` or `[NoInterfaceObject]` extended attributes. It must not be
used on a callback interface.
spelling: anything

https://codereview.chromium.org/2385073002/diff/1/third_party/WebKit/Source/b...
File third_party/WebKit/Source/bindings/bindings.gni (right):

https://codereview.chromium.org/2385073002/diff/1/third_party/WebKit/Source/b...
third_party/WebKit/Source/bindings/bindings.gni:22:
"core/v8/custom/V8HTMLConstructor.cpp",
Let's move this out of 'Custom' since it's infrastructure that a bunch of
elements will use now.

[yurak, 2016-10-03 06:05:16]

Description was changed from

==========
The HTMLConstructor allows "new HTMLElement()" to be called from the console.
Specs: https://html.spec.whatwg.org/#html-element-constructors

Replaced V8HTMLElementCustom with V8HTMLConstructor

Add new extended attribute [HTMLConstructor] to bindings and
IDLExtendedAttributes.txt
  Added description to IDLExtendedAttributes.md and re-organized descriptions
  Added checks for conflicting extended attributes with [HTMLConstructor] in
v8_interface.py
  Edited jinja templates for [HTMLConstructor] interface

Replaced [CustomConstructor] with [HTMLConstructor] in HTMLElement.idl


LayoutTests for custom-elements run correctly with these changes.

BUG=648828
==========

to

==========
The HTMLConstructor allows "new HTMLElement()" to be called from the console.

Specs: https://html.spec.whatwg.org/#html-element-constructors

Replaced V8HTMLElementCustom with V8HTMLConstructor

Add new extended attribute [HTMLConstructor] to bindings and
IDLExtendedAttributes.txt
  Added description to IDLExtendedAttributes.md and re-organized descriptions
  Added checks for conflicting extended attributes with [HTMLConstructor] in
v8_interface.py
  Edited jinja templates for [HTMLConstructor] interface

Replaced [CustomConstructor] with [HTMLConstructor] in HTMLElement.idl


LayoutTests for custom-elements run as expected with these changes.

BUG=648828
==========

[haraken, 2016-10-03 06:13:04]

LGTM

Have we sent an Intent-to-implement to blink-dev@?

https://codereview.chromium.org/2385073002/diff/20001/third_party/WebKit/Sour...
File third_party/WebKit/Source/bindings/core/v8/V8HTMLConstructor.cpp (right):

https://codereview.chromium.org/2385073002/diff/20001/third_party/WebKit/Sour...
third_party/WebKit/Source/bindings/core/v8/V8HTMLConstructor.cpp:22: void
V8HTMLElement::create(const v8::FunctionCallbackInfo<v8::Value>& info) {

I'd rename this to ::htmlConstructor or something. In Blink, ::create normally
means a factory method of the object.

https://codereview.chromium.org/2385073002/diff/20001/third_party/WebKit/Sour...
File third_party/WebKit/Source/bindings/scripts/v8_interface.py (right):

https://codereview.chromium.org/2385073002/diff/20001/third_party/WebKit/Sour...
third_party/WebKit/Source/bindings/scripts/v8_interface.py:341:
'has_html_constructor': bool(html_constructor),

Alphabetical order.

[dominicc (has gone to gerrit), 2016-10-03 08:06:02]

On Mon, Oct 3, 2016 at 3:13 PM, <haraken@chromium.org> wrote:

> LGTM
>
> Have we sent an Intent-to-implement to blink-dev@?
>

There was one a long time ago:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/EDxhDZ-bPkQ/WEFFoWC9...

We could send another one for built-in custom elements specifically,
because there's some new information:
- rniwa has said Apple will "never" ship built-in custom elements.
- Mozilla has started implementing.

I guess it is better to get feedback sooner. What do you think?


> https://codereview.chromium.org/2385073002/diff/20001/
> third_party/WebKit/Source/bindings/core/v8/V8HTMLConstructor.cpp
> File third_party/WebKit/Source/bindings/core/v8/V8HTMLConstructor.cpp
> (right):
>
> https://codereview.chromium.org/2385073002/diff/20001/
> third_party/WebKit/Source/bindings/core/v8/V8HTMLConstructor.cpp#newcode22
> third_party/WebKit/Source/bindings/core/v8/V8HTMLConstructor.cpp:22:
> void V8HTMLElement::create(const v8::FunctionCallbackInfo<v8::Value>&
> info) {
>
> I'd rename this to ::htmlConstructor or something. In Blink, ::create
> normally means a factory method of the object.
>
> https://codereview.chromium.org/2385073002/diff/20001/
> third_party/WebKit/Source/bindings/scripts/v8_interface.py
> File third_party/WebKit/Source/bindings/scripts/v8_interface.py (right):
>
> https://codereview.chromium.org/2385073002/diff/20001/
> third_party/WebKit/Source/bindings/scripts/v8_interface.py#newcode341
> third_party/WebKit/Source/bindings/scripts/v8_interface.py:341:
> 'has_html_constructor': bool(html_constructor),
>
> Alphabetical order.
>
> https://codereview.chromium.org/2385073002/
>

-- 
You received this message because you are subscribed to the Google Groups "Blink
Reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-reviews+unsubscribe@chromium.org.

[dominicc (has gone to gerrit), 2016-10-03 08:06:03]

On Mon, Oct 3, 2016 at 3:13 PM, <haraken@chromium.org> wrote:

> LGTM
>
> Have we sent an Intent-to-implement to blink-dev@?
>

There was one a long time ago:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/EDxhDZ-bPkQ/WEFFoWC9...

We could send another one for built-in custom elements specifically,
because there's some new information:
- rniwa has said Apple will "never" ship built-in custom elements.
- Mozilla has started implementing.

I guess it is better to get feedback sooner. What do you think?


> https://codereview.chromium.org/2385073002/diff/20001/
> third_party/WebKit/Source/bindings/core/v8/V8HTMLConstructor.cpp
> File third_party/WebKit/Source/bindings/core/v8/V8HTMLConstructor.cpp
> (right):
>
> https://codereview.chromium.org/2385073002/diff/20001/
> third_party/WebKit/Source/bindings/core/v8/V8HTMLConstructor.cpp#newcode22
> third_party/WebKit/Source/bindings/core/v8/V8HTMLConstructor.cpp:22:
> void V8HTMLElement::create(const v8::FunctionCallbackInfo<v8::Value>&
> info) {
>
> I'd rename this to ::htmlConstructor or something. In Blink, ::create
> normally means a factory method of the object.
>
> https://codereview.chromium.org/2385073002/diff/20001/
> third_party/WebKit/Source/bindings/scripts/v8_interface.py
> File third_party/WebKit/Source/bindings/scripts/v8_interface.py (right):
>
> https://codereview.chromium.org/2385073002/diff/20001/
> third_party/WebKit/Source/bindings/scripts/v8_interface.py#newcode341
> third_party/WebKit/Source/bindings/scripts/v8_interface.py:341:
> 'has_html_constructor': bool(html_constructor),
>
> Alphabetical order.
>
> https://codereview.chromium.org/2385073002/
>

-- 
You received this message because you are subscribed to the Google Groups
"Chromium-reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.

[haraken, 2016-10-03 08:14:19]

On 2016/10/03 08:06:03, dominicc wrote:
> On Mon, Oct 3, 2016 at 3:13 PM, <mailto:haraken@chromium.org> wrote:
> 
> > LGTM
> >
> > Have we sent an Intent-to-implement to blink-dev@?
> >
> 
> There was one a long time ago:
>
https://groups.google.com/a/chromium.org/d/msg/blink-dev/EDxhDZ-bPkQ/WEFFoWC9...
> 
> We could send another one for built-in custom elements specifically,
> because there's some new information:
> - rniwa has said Apple will "never" ship built-in custom elements.
> - Mozilla has started implementing.
> 
> I guess it is better to get feedback sooner. What do you think?

Hmm, there is no response to
https://groups.google.com/a/chromium.org/d/msg/blink-dev/EDxhDZ-bPkQ/WEFFoWC9...
...

You don't need to get an LG for Intent-to-implement, but I'm not sure if it's a
good idea to start implementing without getting a buy-in of the community. At
least shall we ping the old thread?

[dominicc (has gone to gerrit), 2016-10-04 01:17:22]

On Mon, Oct 3, 2016 at 5:14 PM, <haraken@chromium.org> wrote:

> On 2016/10/03 08:06:03, dominicc wrote:
> > On Mon, Oct 3, 2016 at 3:13 PM, <mailto:haraken@chromium.org> wrote:
> >
> > > LGTM
> > >
> > > Have we sent an Intent-to-implement to blink-dev@?
> > >
> >
> > There was one a long time ago:
> >
> https://groups.google.com/a/chromium.org/d/msg/blink-dev/
> EDxhDZ-bPkQ/WEFFoWC9BQAJ
> >
> > We could send another one for built-in custom elements specifically,
> > because there's some new information:
> > - rniwa has said Apple will "never" ship built-in custom elements.
> > - Mozilla has started implementing.
> >
> > I guess it is better to get feedback sooner. What do you think?
>
> Hmm, there is no response to
> https://groups.google.com/a/chromium.org/d/msg/blink-dev/
> EDxhDZ-bPkQ/WEFFoWC9BQAJ
> ...
>
> You don't need to get an LG for Intent-to-implement, but I'm not sure if
> it's a
> good idea to start implementing without getting a buy-in of the community.
> At
> least shall we ping the old thread?
>
>
> https://codereview.chromium.org/2385073002/
>

The old thread is really old. I'll start a new thread today.

-- 
You received this message because you are subscribed to the Google Groups "Blink
Reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-reviews+unsubscribe@chromium.org.

[dominicc (has gone to gerrit), 2016-10-04 01:17:23]

On Mon, Oct 3, 2016 at 5:14 PM, <haraken@chromium.org> wrote:

> On 2016/10/03 08:06:03, dominicc wrote:
> > On Mon, Oct 3, 2016 at 3:13 PM, <mailto:haraken@chromium.org> wrote:
> >
> > > LGTM
> > >
> > > Have we sent an Intent-to-implement to blink-dev@?
> > >
> >
> > There was one a long time ago:
> >
> https://groups.google.com/a/chromium.org/d/msg/blink-dev/
> EDxhDZ-bPkQ/WEFFoWC9BQAJ
> >
> > We could send another one for built-in custom elements specifically,
> > because there's some new information:
> > - rniwa has said Apple will "never" ship built-in custom elements.
> > - Mozilla has started implementing.
> >
> > I guess it is better to get feedback sooner. What do you think?
>
> Hmm, there is no response to
> https://groups.google.com/a/chromium.org/d/msg/blink-dev/
> EDxhDZ-bPkQ/WEFFoWC9BQAJ
> ...
>
> You don't need to get an LG for Intent-to-implement, but I'm not sure if
> it's a
> good idea to start implementing without getting a buy-in of the community.
> At
> least shall we ping the old thread?
>
>
> https://codereview.chromium.org/2385073002/
>

The old thread is really old. I'll start a new thread today.

-- 
You received this message because you are subscribed to the Google Groups
"Chromium-reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.

[yurak, 2016-10-04 05:37:34]

I renamed ::create to ::HTMLConstructor. I made a few new changes to two files
listed below so PTL! :)

.../scripts/idl_definitions.py
.../scripts/v8_methods.py

I ran LayoutTests for custom-elements again and they run as expected with these
changes.

[haraken, 2016-10-04 05:38:30]

LGTM, assuming there's no objection on the Intent-to-implement dominicc is going
to send.

[bashi, 2016-10-04 05:53:50]

bashi@chromium.org changed reviewers:
+ bashi@chromium.org

[bashi, 2016-10-04 05:53:51]

https://codereview.chromium.org/2385073002/diff/60001/third_party/WebKit/Sour...
File third_party/WebKit/Source/bindings/scripts/idl_definitions.py (right):

https://codereview.chromium.org/2385073002/diff/60001/third_party/WebKit/Sour...
third_party/WebKit/Source/bindings/scripts/idl_definitions.py:973:
html_constructors =
[IdlOperation.constructor_from_arguments_node('HTMLConstructor', idl_name,
None)]
Could you help me understand why we need to use a list here?

- If there are more than one HTMLConstructors, this seems not correct (Ignoring
some constructors?).
- If there is only one HTMLConstructor, we can store it directly.

Also, why do we need to store |html_constructors| in IdlInterface?

[yurak, 2016-10-04 06:29:46]

On 2016/10/04 at 05:53:51, bashi wrote:
>
https://codereview.chromium.org/2385073002/diff/60001/third_party/WebKit/Sour...
> File third_party/WebKit/Source/bindings/scripts/idl_definitions.py (right):
> 
>
https://codereview.chromium.org/2385073002/diff/60001/third_party/WebKit/Sour...
> third_party/WebKit/Source/bindings/scripts/idl_definitions.py:973:
html_constructors =
[IdlOperation.constructor_from_arguments_node('HTMLConstructor', idl_name,
None)]
> Could you help me understand why we need to use a list here?
> 
> - If there are more than one HTMLConstructors, this seems not correct
(Ignoring some constructors?).
> - If there is only one HTMLConstructor, we can store it directly.
> 
> Also, why do we need to store |html_constructors| in IdlInterface?

Turns out I didn't need to make changes to those two files so I reverted the
changes. (Thanks bashi)

[bashi, 2016-10-04 06:44:46]

lgtm on my side.

https://codereview.chromium.org/2385073002/diff/80001/third_party/WebKit/Sour...
File third_party/WebKit/Source/bindings/scripts/v8_interface.py (right):

https://codereview.chromium.org/2385073002/diff/80001/third_party/WebKit/Sour...
third_party/WebKit/Source/bindings/scripts/v8_interface.py:295: html_constructor
= 'HTMLConstructor' in extended_attributes
nit: html_constructor -> has_html_constructor ?

https://codereview.chromium.org/2385073002/diff/80001/third_party/WebKit/Sour...
third_party/WebKit/Source/bindings/scripts/v8_interface.py:298: if
('Constructor' in extended_attributes) or ('NoInterfaceObject' in
extended_attributes):
nit: It seems that you can drop ('Constructor' in extended_attributes)

https://codereview.chromium.org/2385073002/diff/80001/third_party/WebKit/Sour...
third_party/WebKit/Source/bindings/scripts/v8_interface.py:342:
'has_html_constructor': bool(html_constructor),
nit: |html_constructor| is already a bool value so you can drop bool()

[Yuki, 2016-10-04 06:51:04]

yukishiino@chromium.org changed reviewers:
+ yukishiino@chromium.org

[Yuki, 2016-10-04 06:51:05]

lgtm

https://codereview.chromium.org/2385073002/diff/80001/third_party/WebKit/Sour...
File third_party/WebKit/Source/bindings/IDLExtendedAttributes.md (right):

https://codereview.chromium.org/2385073002/diff/80001/third_party/WebKit/Sour...
third_party/WebKit/Source/bindings/IDLExtendedAttributes.md:303: Standard:
[HTMLConstructor](https://html.spec.whatwg.org/#html-element-constructors)
nit: https://html.spec.whatwg.org/multipage/dom.html#html-element-constructors

Could you use "multipage" version rather than the single page version?
The single page version is too heavy.

https://codereview.chromium.org/2385073002/diff/80001/third_party/WebKit/Sour...
File third_party/WebKit/Source/bindings/scripts/v8_interface.py (right):

https://codereview.chromium.org/2385073002/diff/80001/third_party/WebKit/Sour...
third_party/WebKit/Source/bindings/scripts/v8_interface.py:297: #
https://html.spec.whatwg.org/#html-element-constructors
nit: https://html.spec.whatwg.org/multipage/dom.html#html-element-constructors

[yurak, 2016-10-05 01:51:57]

The CQ bit was checked by yurak@google.com

[yurak, 2016-10-05 01:51:58]

The patchset sent to the CQ was uploaded after l-g-t-m from
dominicc@chromium.org, haraken@chromium.org, bashi@chromium.org,
yukishiino@chromium.org
Link to the patchset: https://codereview.chromium.org/2385073002/#ps100001
(title: "Renamed V8HTMLElement constructor to HTMLConstructor")

[yurak, 2016-10-05 01:52:10]

The CQ bit was unchecked by yurak@google.com

[yurak, 2016-10-05 01:52:55]

Description was changed from

==========
The HTMLConstructor allows "new HTMLElement()" to be called from the console.

Specs: https://html.spec.whatwg.org/#html-element-constructors

Replaced V8HTMLElementCustom with V8HTMLConstructor

Add new extended attribute [HTMLConstructor] to bindings and
IDLExtendedAttributes.txt
  Added description to IDLExtendedAttributes.md and re-organized descriptions
  Added checks for conflicting extended attributes with [HTMLConstructor] in
v8_interface.py
  Edited jinja templates for [HTMLConstructor] interface

Replaced [CustomConstructor] with [HTMLConstructor] in HTMLElement.idl


LayoutTests for custom-elements run as expected with these changes.

BUG=648828
==========

to

==========
Implemented HTMLConstructor extended attribute.

Specs: https://html.spec.whatwg.org/#html-element-constructors

Replaced V8HTMLElementCustom with V8HTMLConstructor

Add new extended attribute [HTMLConstructor] to bindings and
IDLExtendedAttributes.txt
  Added description to IDLExtendedAttributes.md and re-organized descriptions
  Added checks for conflicting extended attributes with [HTMLConstructor] in
v8_interface.py
  Edited jinja templates for [HTMLConstructor] interface

Replaced [CustomConstructor] with [HTMLConstructor] in HTMLElement.idl


LayoutTests for custom-elements run as expected with these changes.

BUG=648828
==========

[yurak, 2016-10-05 01:53:17]

Description was changed from

==========
Implemented HTMLConstructor extended attribute.

Specs: https://html.spec.whatwg.org/#html-element-constructors

Replaced V8HTMLElementCustom with V8HTMLConstructor

Add new extended attribute [HTMLConstructor] to bindings and
IDLExtendedAttributes.txt
  Added description to IDLExtendedAttributes.md and re-organized descriptions
  Added checks for conflicting extended attributes with [HTMLConstructor] in
v8_interface.py
  Edited jinja templates for [HTMLConstructor] interface

Replaced [CustomConstructor] with [HTMLConstructor] in HTMLElement.idl


LayoutTests for custom-elements run as expected with these changes.

BUG=648828
==========

to

==========
Implemented HTMLConstructor extended attribute.

Specs: https://html.spec.whatwg.org/#html-element-constructors

Replaced V8HTMLElementCustom with V8HTMLConstructor

Add new extended attribute [HTMLConstructor] to bindings and
IDLExtendedAttributes.txt
  Added description to IDLExtendedAttributes.md and re-organized descriptions
  Added checks for conflicting extended attributes with [HTMLConstructor] in
v8_interface.py
  Edited jinja templates for [HTMLConstructor] interface

Replaced [CustomConstructor] with [HTMLConstructor] in HTMLElement.idl

BUG=648828
==========

[yurak, 2016-10-05 01:53:23]

The CQ bit was checked by yurak@google.com

[commit-bot: I haz the power, 2016-10-05 01:53:40]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-05 03:47:34]

Committed patchset #6 (id:100001)

[commit-bot: I haz the power, 2016-10-05 03:51:41]

Description was changed from

==========
Implemented HTMLConstructor extended attribute.

Specs: https://html.spec.whatwg.org/#html-element-constructors

Replaced V8HTMLElementCustom with V8HTMLConstructor

Add new extended attribute [HTMLConstructor] to bindings and
IDLExtendedAttributes.txt
  Added description to IDLExtendedAttributes.md and re-organized descriptions
  Added checks for conflicting extended attributes with [HTMLConstructor] in
v8_interface.py
  Edited jinja templates for [HTMLConstructor] interface

Replaced [CustomConstructor] with [HTMLConstructor] in HTMLElement.idl

BUG=648828
==========

to

==========
Implemented HTMLConstructor extended attribute.

Specs: https://html.spec.whatwg.org/#html-element-constructors

Replaced V8HTMLElementCustom with V8HTMLConstructor

Add new extended attribute [HTMLConstructor] to bindings and
IDLExtendedAttributes.txt
  Added description to IDLExtendedAttributes.md and re-organized descriptions
  Added checks for conflicting extended attributes with [HTMLConstructor] in
v8_interface.py
  Edited jinja templates for [HTMLConstructor] interface

Replaced [CustomConstructor] with [HTMLConstructor] in HTMLElement.idl

BUG=648828

Committed: https://crrev.com/6ad512924f794cd4cbee80246106716993919bde
Cr-Commit-Position: refs/heads/master@{#423068}
==========

[commit-bot: I haz the power, 2016-10-05 03:51:42]

Patchset 6 (id:??) landed as
https://crrev.com/6ad512924f794cd4cbee80246106716993919bde
Cr-Commit-Position: refs/heads/master@{#423068}