.ajax-progress--fullscreen z-index should be higher than .ui-dialog when triggered in a modal.

This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.

per #9 going to 9999 is too high. Whatever version is decided and why should be added to the issue summary please.

Currently .ui-dialog have a z-index of 1260. As suggested in #9, we can have z-index as 1500.

--jui-dialog-z-index: 1260;
.ui-dialog {
  z-index: var(--jui-dialog-z-index);
}

Updated issue summary and attached patch with interdiff for same. please review

The last submitted patch, 22: 3118813-22.patch, failed testing. View results →

Unrelated failure. restoring the status

#9 mentioned adding some research to land on 1500. Can you provide what that was and add to the IS please.

Adding reroll for 10.1.x as above patch failed on 10.1.x.
Removed changes of "b/core/themes/stable/css/system/components/ajax-progress.module.css" because it doesn't exist in 10.1.x

Doesn't answer #25

Tagging with Field UX as upcoming changes will potentially add more usages of ajax progress in dialogs.

Setting the z-index for .ajax-progress--fullscreen class to 1300 because the z-index for .ui-dialog class is 1260 and any thing which is above 1260 shall work.You can find the z-indexes in drupal → for reference.

Thank for the reasoning. Added that to the issue summary too

Re #31

Setting the z-index for .ajax-progress--fullscreen class to 1300 because the z-index for .ui-dialog class is 1260 and any thing which is above 1260 shall work.You can find the z-indexes in drupal for reference.

Based on this rationale, the z-index should be 1261 then as we want to avoid z-index creep. Either the z-index or the explanation should be modified.

Good suggestion @bnjmnm, thanks @Utkarsh_33 for the prompt change

Tested manually with every core theme. This is fixed where it needs to be fixed, and doesn't introduce changes where nothing needs to be fixed. Committed to 10.1.x.

Automatically closed - issue fixed for 2 weeks with no activity.