Problem with paper-input inside paper-item added via <content>

[SPessall]

I have a recurrence of issue #28, where a paper-input element located inside a paper-item does not accept the space character.

The reason that the fix for the linked issue does not work in my case is that the paper-input element is added via the insertion point.

<paper-item>
    <content></content>
</paper-item>

From what I have gathered the cause of the problems is that due to using the content element the paper-input is part of the shadow dom.

I have seen that the spaceKeyDownHandler(), which paper-item inherits from the iron-button-state behavior tries to detect whether the target of the keyboard event handles the input itself. But it assumes that children located inside the shadow dom don't do this.

At the moment it is unclear to me whether this is a bug or working as intended, but to me it seems like adding a paper-input through the content element should work correctly.

[schlm3]

I have this problem too while using https://github.com/Collaborne/paper-collapse-item
It uses the paper-item like that:

<paper-item>
	<paper-item-body>
		<div class="header" on-tap="_toggleOpened">
			....
		</div>
		<iron-collapse class="content" opened="{{opened}}">
			<slot></slot>
		</iron-collapse>
	</paper-item-body>
</paper-item>

The paper-collapse-item is used thatlike:

<paper-collapse-item header="Spacebar Problem Demo" opened>
	<paper-input label="Enter Text with spaces"/>
</paper-collapse-item>

results in not able to enter spaces in that input field.

[schlm3]

Verified, that this is still a problem in Polymer 2.0.x (while I need a fix for 1.0.x).

[SPessall]

Pity, I had hoped that this problem would be resolved with an upgrade to Polymer 2. We also stumbled over this problem while using the paper-collapse-item.

Currently we use a workaround in our components, where we overwrite _spaceKeyDownHandler with an empty function in the embedded paper-item components like this:

polymerObject.$$('paper-collapse-item').$$('paper-item')._spaceKeyDownHandler = function () {};

Up to now we have not detected any negative consequences due to this workaround.

[schlm3]

Verified, that code from SPessall is working.
But it would still be good if the cause would be fixed in polymer-item.