* keyboard navigation for defects 1722611,1722618
* Fixes for keyboard navigation of add new clause,edit,remove property,insert filter line, remove filter line
* Revert "keyboard navigation for defects 1722611,1722618"
This reverts commit 9383609a22.
* html,css changes corected after reversion
* Revert "html,css changes corected after reversion"
This reverts commit 712e0e0c1e.
* committing changes for the keyboard navigation
* format fixes
* changes to addcollectionpanel.test.tsx snp file
* changes in infotooltip for defct
* Revert "changes in infotooltip for defct"
This reverts commit ca9833e208.
* commit for tooltip in defect 1704149
* Revert "commit for tooltip in defect 1704149"
This reverts commit 44766e8213.
* InfoTooltip changes
* update snapshot
* defect1722595 Bug 1722595: [Screen readers Azure Cosmos DB Scale& Settings: Screen reader (NVDA) is not announcing status message which is displayed on the screen after radio button is selected under scale tab.
* more options in delete entity dialog is not accessible through keyboard
* Revert "more options in delete entity dialog is not accessible through keyboard"
This reverts commit 23a05ef18e.
* more options in delete entity dialog is not accessible throgh keyboard
* remove native html with role='alert' for messagebar
* role added for messagebar fluentui component
When building queries with projections, the resulting query does not include the "id" property as part of the projection. The "id" property is used by the results grid to display as the RowKey so the result is queries wih projections do not show the RowKey.
This change fixes this by including "id" as part of the projections.
- Make sure we pass the error message string instead of an error object when we call `TelemetryProcessor.traceFailure` since TelemetryProcessor will call `JSON.stringify` on the error object which would result in an empty object
- Removed ErrorParserUtility since it only works on specific error types. We can just log the full error message and manually derive information we need from the message.
- Added option to include stack trace in `getErrorMessage`. This is useful for figuring out where the client side script errors are coming from.
- Some minor refactors
The DataTable control creates 3 tables in the DOM, one for the header, one for the body and one for the footer. Because of this when navigating through the tablem it says "leaving table", when it is really the same table. It seems this is not the default and because of the option **dom: "RZlfrtip"**, the DataTable is created this way.
If I remove that setting, it will only create one table, BUT other things break, because there is a lot of custom DOM manipulation assuming the DOM was the way it was before (gross). This make me question if we wanted this on purpose to maybe solve a cross browser scrolling issue.
Instead I decided to leave it as is, until migrating to Microsoft's Fluent UI is prioritized. However I did add a summary attribute to each table, so that when listening to the narrator, it make more sense when leaving one part of the table into another part of the table. While not optimal, it should at least satisfy accessibility concern of it being confusing.
Things like ConfigContext.BACKEND_ENDPOINT are dynamically changed, and assigning them statically like this only bypasses that mechanism :(
Co-authored-by: Steve Faulkner <471400+southpolesteve@users.noreply.github.com>
