You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These URLs are resolved relative to category.component.ts, so Angular looks for app/category/app/category/category.component.html and .css and the demo cannot compile. Use paths relative to this component file (./category.component.html and ./category.component.css).
The prompt editor only supplies a placeholder and no programmatic label. The generated input therefore has no reliable accessible name for screen readers (unlike the response editor below, which sets aria-label); pass [inputAttr] with a label such as Ask AI Assistant.
These URLs are resolved relative to detail-view.component.ts, so Angular looks for app/detail-view/app/detail-view/detail-view.component.html and .css and the demo cannot compile. Use ./detail-view.component.html and ./detail-view.component.css instead.
The prompt editor only supplies a placeholder and no programmatic label. The generated input therefore has no reliable accessible name for screen readers (unlike the response editor below, which sets aria-label); pass an inputAttr with a label such as Ask AI Assistant.
This paragraph says that submitting the prompt expands the detail row, but the prompt controls only exist after the user has already expanded that row (as described above). Please make the sequence explicit so the demo instructions do not mislead users.
To surface AI-generated insights within the DataGrid, this sample uses the [master-detail template](/Documentation/ApiReference/UI_Components/dxDataGrid/Configuration/masterDetail/#component) together with DevExtreme [TextBox](/Documentation/Guide/UI_Components/TextBox/Overview/) and [Button](/Documentation/Guide/UI_Components/Button/Overview/) components. A [ButtonGroup](/Documentation/Guide/UI_Components/ButtonGroup/Getting_Started_with_ButtonGroup/) provides prompt suggestions, delivering an experience similar to the DevExtreme Chat [Suggestions](/Demos/WidgetsGallery/Demo/Chat/PromptSuggestions/) demo. When a user submits a prompt, the corresponding detail row expands and displays a [LoadPanel](/Documentation/Guide/UI_Components/LoadPanel/Overview/) while the AI processes the request. Once generation is complete, the response is rendered in a [read-only](/Documentation/ApiReference/UI_Components/dxTextArea/Configuration/#readOnly) [TextArea](/Documentation/Guide/UI_Components/TextArea/Getting_Started_with_TextArea/), allowing users to review AI-generated content directly within the DataGrid without leaving the current context.
The prompt editor only supplies a placeholder and no programmatic label. The generated input therefore has no reliable accessible name for screen readers (unlike the response editor below, which sets aria-label); pass an inputAttr with a label such as Ask AI Assistant.
This paragraph says that submitting the prompt expands the detail row, but the prompt controls only exist after the user has already expanded that row (as described above). Please make the sequence explicit so the demo instructions do not mislead users.
To surface AI-generated insights within the DataGrid, this sample uses the [master-detail template](/Documentation/ApiReference/UI_Components/dxDataGrid/Configuration/masterDetail/#component) together with DevExtreme [TextBox](/Documentation/Guide/UI_Components/TextBox/Overview/) and [Button](/Documentation/Guide/UI_Components/Button/Overview/) components. A [ButtonGroup](/Documentation/Guide/UI_Components/ButtonGroup/Getting_Started_with_ButtonGroup/) provides prompt suggestions, delivering an experience similar to the DevExtreme Chat [Suggestions](/Demos/WidgetsGallery/Demo/Chat/PromptSuggestions/) demo. When a user submits a prompt, the corresponding detail row expands and displays a [LoadPanel](/Documentation/Guide/UI_Components/LoadPanel/Overview/) while the AI processes the request. Once generation is complete, the response is rendered in a [read-only](/Documentation/ApiReference/UI_Components/dxTextArea/Configuration/#readOnly) [TextArea](/Documentation/Guide/UI_Components/TextArea/Getting_Started_with_TextArea/), allowing users to review AI-generated content directly within the DataGrid without leaving the current context.
The prompt editor only supplies a placeholder and no programmatic label. The generated input therefore has no reliable accessible name for screen readers (unlike the response editor below, which sets aria-label); pass an input-attr with a label such as Ask AI Assistant. apps/demos/Demos/DataGrid/AIPoweredDetailView/description.md:15
This paragraph says that submitting the prompt expands the detail row, but the prompt controls only exist after the user has already expanded that row (as described above). Please make the sequence explicit so the demo instructions do not mislead users. apps/demos/Demos/DataGrid/AIPoweredDetailView/jQuery/index.js:118
The prompt editor only supplies a placeholder and no programmatic label. The generated input therefore has no reliable accessible name for screen readers (unlike the response editor below, which sets aria-label); pass inputAttr with a label such as Ask AI Assistant. apps/demos/Demos/DataGrid/AIPoweredDetailView/jQuery/index.js:103
When a row is collapsed, dxremove aborts the request and the detail widgets are disposed before this promise's finally runs. The unconditional option/toggleLoadingState calls can therefore operate on disposed widgets (and the same issue occurs if an older request finishes after a newer detail is active). Only update these controls when activeAbortController === controller; otherwise return from the completion path.
Aborting the request when the row collapses rejects getAIResponse, but this catch treats that expected cancellation as a real failure and sets the error state. Collapsed master-detail content can remain mounted and hidden, so reopening the row then shows “An unexpected error occurred” even though no request failed. Ignore aborted controllers here instead of entering the error state.
Aborting the request when the row collapses rejects getAIResponse, but this catch treats that expected cancellation as a real failure and sets the error state. Collapsed master-detail content can remain mounted and hidden, so reopening the row then shows “An unexpected error occurred” even though no request failed. Ignore aborted controllers here instead of entering the error state.
Aborting the request when the row collapses rejects getAIResponse, but this catch treats that expected cancellation as a real failure and sets the error state. Collapsed master-detail content can remain mounted and hidden, so reopening the row then shows “An unexpected error occurred” even though no request failed. Ignore aborted controllers here instead of entering the error state.
Aborting the request when the row collapses rejects getAIResponse, but this catch treats that expected cancellation as a real failure and sets the error state. Collapsed master-detail content can remain mounted and hidden, so reopening the row then shows “An unexpected error occurred” even though no request failed. Ignore aborted controllers here instead of entering the error state. apps/demos/Demos/DataGrid/AIPoweredDetailView/jQuery/index.js:97
Aborting the request when the row collapses rejects getAIResponse, but this catch treats that expected cancellation as a real failure and adds the error message. Collapsed master-detail content can remain mounted and hidden, so reopening the row then shows “An unexpected error occurred” even though no request failed. Ignore aborted controllers here; when there is no prior response, restore the initial message instead.
This description says submitting a prompt expands the corresponding detail row, but the prompt controls only exist after the user has already expanded a row and none of the implementations expands a row from submission. This misstates the interaction; describe the detail row as already expanded rather than claiming submission expands it.
When a detail row is collapsed, onRowCollapsing aborts the request and the row is then removed, but this catch/finally still updates the response editor, message, load panel, and event target. The aborted promise resumes after the detail widgets may be disposed, so collapsing a row during a request can update detached instances or throw; skip these UI operations when controller.signal.aborted (while still clearing the active controller).
…owered Detail View one
481 e2e and 6 demo etalons, taken from the CI run of the merge. Main re-shot
the fluent, generic and material pairs of almost all of them for Chrome 153
in DevExpress#35284, and the fluent-next ones show the same text shifts. Three of the
e2e ones also still had the pager from before its selected page turned bold.
DataGrid-AIPoweredDetailView came from main (DevExpress#34775) without a fluent-next
etalon.
…emo reads it
The DataGrid AIPoweredDetailView demo from main (DevExpress#34775) sizes its prompt
editor and submit row with it in all five frameworks. It goes back on :root,
off public-renames.json and into the kept allowlist; the baselines follow.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.