webcomponents / webcomponents/custom-elements-everywhere

Add test for setting properties with primitive values

Open
#90 6 comments 1 reaction 0 assignees View on GitHub
Additional Tests
Dominant language
JavaScript
Stars
1.3k
Forks
108
PR merge metrics
No merged PRs in 30d

Description

Right now primitive values are allowed to be set as either an attribute or a property. Since properties and attributes are two separate APIs, custom elements could require that a value is passed in via one API or the other. I do think it's fairly common that there are properties not set from corresponding attributes.

There should be tests that set a property to a `boolean`|`number`|`string`|`null`|`undefined` and requires that the _property_ is set, not the attribute.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.