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

deepRelatedTargets and touch.deepTargets #76

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

deepRelatedTargets and touch.deepTargets #76

hayatoito opened this issue May 25, 2015 · 8 comments

Comments

@hayatoito
Copy link
Contributor

Title: [Shadow] investigate if there should be deepRelatedTargets and touch.deepTargets (bugzilla: 28560)

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


comment: 0
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28560#c0
Olli Pettay wrote on 2015-04-26 18:25:01 +0000.

.


comment: 1
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28560#c1
Hayato Ito wrote on 2015-04-27 01:30:58 +0000.

The motivation is that we can't use event.deepPath[0] in either case, isn't it?


comment: 2
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28560#c2
Anne wrote on 2015-04-27 03:06:02 +0000.

Yes, these properties are changed but their original values are not otherwise exposed.

(There might also be value in event.deepTarget as a clearer event.deepPath[0], just like event.target is short for a conceptual event.path[0]...)


comment: 3
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28560#c3
Anne wrote on 2015-04-27 11:25:19 +0000.

Also:

deepOffsetX/Y

@hayatoito
Copy link
Contributor Author

I think it's easy to add deepRelatedTarget and so on. However, I'd like to see the actual use cases.
Let me defer this to v2. If someone has a use case, please update this issue. I'm okay to have this in v1.

@hayatoito hayatoito added v2 and removed v1 labels Jun 4, 2015
@annevk
Copy link
Collaborator

annevk commented Jun 9, 2015

What worries me a bit is that we have a weird mix with retargeting while also wanting event delegation. If you want actual event delegation, you want the original values for all these properties (also offset*).

@hayatoito
Copy link
Contributor Author

Let me close this issue since there is lack of interest. Please feel free to reopen if you are interested in.

@annevk
Copy link
Collaborator

annevk commented Mar 16, 2016

What I would like to know is how you can use deepPath without the corresponding deepRelatedTargets, etc. Perhaps the latter is only relevant for a subset of events, but it seems the model is inconsistent here.

@annevk annevk reopened this Mar 16, 2016
@hayatoito
Copy link
Contributor Author

I think deepPath is useful itself, without having deepRelatedTarget.
For consistency, we might want to have deepRelatedTarget, however, I have never heard a demand for that.
I'm okay to have deepRelatedTarget, but I thought we should add it when we hear a demand for that.

@hayatoito
Copy link
Contributor Author

Let me keep this open. If someone has a use case for deepRelatedTarget, please let us know that.

@hayatoito hayatoito changed the title [Shadow] investigate if there should be deepRelatedTargets and touch.deepTargets (bugzilla: 28560) deepRelatedTargets and touch.deepTargets Mar 17, 2016
@annevk
Copy link
Collaborator

annevk commented Mar 17, 2016

Maybe it's just that we don't have many usage scenarios for relatedTarget?

@annevk
Copy link
Collaborator

annevk commented Oct 19, 2016

I think you were right for closing this. The inconsistency still puzzles me, but that's not enough reason to keep this open. Apologies.

@annevk annevk closed this as completed Oct 19, 2016
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