Skip to content
This repository was archived by the owner on Jun 3, 2020. It is now read-only.

Spec: make ResizeObserverEntry private #35

Closed
atotic opened this issue Dec 16, 2016 · 3 comments
Closed

Spec: make ResizeObserverEntry private #35

atotic opened this issue Dec 16, 2016 · 3 comments

Comments

@atotic
Copy link
Collaborator

atotic commented Dec 16, 2016

ResizeObserverEntry constructor should not be publicly accessible.

https://bugs.chromium.org/p/chromium/issues/detail?id=674520

@RByers
Copy link
Member

RByers commented Mar 4, 2017

Aren't there scenarios where some library may want to synthesize these? Filed w3ctag/design-principles#51 to discuss the general principle.

@atotic
Copy link
Collaborator Author

atotic commented Mar 6, 2017

I had no strong reasons for not including the constructor, it the was the general rule: "do not write code you won't use".
If there is a webapi rule "constructors are exposed by default", I am happy to implement it.

@tabatkins
Copy link

Yes, there is a general rule that constructors should be available unless there's good reasons to avoid them (for example, if a valid object requires private browser state, which the user can't reasonably access).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants