Bug report #20743
After handling bad layers, no unsaved state
|Affected QGIS version:||3.4.2||Regression?:||No|
|Operating System:||Win7||Easy fix?:||No|
|Pull Request or Patch supplied:||Yes||Resolution:|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||28563|
Sorry if this should be going under feature request, but I think it's problematic.
After handling bad layers, QGIS does not set the project to an unsaved state, so a person could close the project from that point and not have the option to save with the updated layer sources.
Checked in 3.4 and 3.5 (Which thank you for the options to hang onto bad layers in 3.5. That's a feature I've wanted for a long time! :) )