component.prop("id") returned with component.find("#foo")

Is this a bug report?

Yes

Environment

enzyme@3.0.0

Steps to Reproduce

When a component is mounted with JSDOM the selector library does not differentiate props.id and element.id

using react router as an example

const test = mount(<Link id="foo" />)
const fooLink = test.find("#foo) <-- returns 2 nodes (<Link /> + <a>)

Expected Behavior

I would not expect a custom component with the prop id to be returned when querying with a CSS selector.

• test.findWhere(n => n.prop("id") === foo) <-- expect to return 2 nodes
• test.find("#foo") <-- expect to return a single node

[conartist6]

I have opened #1907 for the problems which occur regardless of this issue.

[conartist6]

Perhaps all that needs to be done is for there to be a convenience API, something like findHost which was a shortcut for hostNodes().find() At least having such a thing be present in documentation would give it more visibility and allow the find documentation to call out the circumstance in which using it would be appropriate.