On polyfilled browsers, composed custom events do not propagate across the full composed path - instead they're swallowed once they hit the vaadin-grid element.
Though I think it's likely this is a Shady DOM bug, I've only been able to reproduce it with the vaadin-grid component so far. I do intend to raise this up (either on webcomponentsjs, shadydom or vaadin) but I need a little more time to throw together a clean JS fiddle to reproduce this.
For the short term, I've worked around this by dispatching the item-action and item-save events from vaadin-grid instead of a component nested within it. I've also added a couple tests for this issue, and tweaked travis/wct to get tests passing across all platforms.
Fixes https://github.com/predixdesignsystem/px-data-grid/issues/805
On polyfilled browsers, composed custom events do not propagate across the full composed path - instead they're swallowed once they hit the
vaadin-grid
element.Though I think it's likely this is a Shady DOM bug, I've only been able to reproduce it with the
vaadin-grid
component so far. I do intend to raise this up (either on webcomponentsjs, shadydom or vaadin) but I need a little more time to throw together a clean JS fiddle to reproduce this.For the short term, I've worked around this by dispatching the
item-action
anditem-save
events fromvaadin-grid
instead of a component nested within it. I've also added a couple tests for this issue, and tweaked travis/wct to get tests passing across all platforms.