search

IgniteUI / igniteui-blazor-examples

samples browser app and individual samples on how to use Ignite UI for Blazor components
https://infragistics.com/blazor-client/samples
12 stars 10 forks source link

Grid - Column Moving Sample throws error when clicking on pin icon #308

Open IGvaleries opened 1 year ago

IGvaleries commented 1 year ago

goto grid - column moving options https://staging.infragistics.com/blazor-client/samples/grids/grid/column-moving-options open dev tools click the red pin in the header of one of the pinned columns

Result: Uncaught DOMException: Failed to execute 'setPointerCapture' on 'Element': InvalidStateError at Hq.onPointerDown (https://localhost:44317/_content/IgniteUI.Blazor/igniteui-angular-elements.6626527c16f60817a0fa.bundle.js:2:567221) at Hq.onPointerDown (https://localhost:44317/_content/IgniteUI.Blazor/igniteui-angular-elements.6626527c16f60817a0fa.bundle.js:2:1515342) at t._next (https://localhost:44317/_content/IgniteUI.Blazor/igniteui-angular-elements.6626527c16f60817a0fa.bundle.js:2:562541) at t.__tryOrUnsub (https://localhost:44317/_content/IgniteUI.Blazor/igniteui-angular-elements.6626527c16f60817a0fa.bundle.js:2:60772) at t.next (https://localhost:44317/_content/IgniteUI.Blazor/igniteui-angular-elements.6626527c16f60817a0fa.bundle.js:2:59937) at t._next (https://localhost:44317/_content/IgniteUI.Blazor/igniteui-angular-elements.6626527c16f60817a0fa.bundle.js:2:59034) at t.next (https://localhost:44317/_content/IgniteUI.Blazor/igniteui-angular-elements.6626527c16f60817a0fa.bundle.js:2:58705) at t._next (https://localhost:44317/_content/IgniteUI.Blazor/igniteui-angular-elements.6626527c16f60817a0fa.bundle.js:2:59034) at t.next (https://localhost:44317/_content/IgniteUI.Blazor/igniteui-angular-elements.6626527c16f60817a0fa.bundle.js:2:58705) at HTMLElement. (https://localhost:44317/_content/IgniteUI.Blazor/igniteui-angular-elements.6626527c16f60817a0fa.bundle.js:2:82092)

HUSSAR-mtrela commented 1 year ago

@agoldenbaum check if this is an issue in sample or product

agoldenbaum commented 1 year ago

This behavior also exists in the Web Component and appears to be a product bug. It was logged in the igniteui-angular repository here: https://github.com/IgniteUI/igniteui-angular/issues/12874. Marking this blocked and bug: in-product. Also downgrading the "severity: critical" as the sample still works fine - it just throws an error in the console.