Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Shadow]: Distribution needs to not be observable (bugzilla: 27994) #87

Closed
hayatoito opened this issue May 25, 2015 · 2 comments
Closed

Comments

@hayatoito
Copy link
Contributor

Title: [Shadow]: Distribution needs to not be observable (bugzilla: 27994)

Migrated from: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27994


comment: 0
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27994#c0
Anne wrote on 2015-02-10 15:35:35 +0000.

"If any condition which affects the distribution result changes, the distribution result must be updated before any use of the distribution result."

It seems both layout and events make use of the distribution result. That would be worth mentioning I think to make it clear what the observable bits are.

However, if events make use of them, wouldn't we be able to work out when distribution happens by firing synthetic events?

And how does this work for ranges that can reach into the shadow DOM? Wouldn't we get problems there too with how deterministic things are?


comment: 1
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27994#c1
Dimitri Glazkov wrote on 2015-02-10 17:00:18 +0000.

There's a bit more discusson here: https://soundcloud.com/dglazkov/polymer-master


comment: 2
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27994#c2
Dimitri Glazkov wrote on 2015-02-10 17:12:30 +0000.

(In reply to Dimitri Glazkov from comment #1)

There's a bit more discusson here:
https://soundcloud.com/dglazkov/polymer-master

Doh. https://gist.github.com/dglazkov/ce96f673b0b2ce7b8c55


comment: 3
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27994#c3
Anne wrote on 2015-04-23 21:09:52 +0000.

See also bug 28443 which discusses this very same issue.


comment: 4
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27994#c4
Anne wrote on 2015-04-27 05:45:56 +0000.

This might be moot if we get an API.

@hayatoito
Copy link
Contributor Author

Could someone summarize what actions should we take on this issue?
The wording of the spec needs to be updated? Or something else?

I'm thinking of closing this issue unless this issue is blocking something for v1.

@hayatoito
Copy link
Contributor Author

Let me close this issue tentatively since we don't have an urgent action items for this issue.

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

No branches or pull requests

2 participants