Collecting for Export marks document as edited
Select 'Export as Resource' and the document will become 'Edited'
Illustrator 29.0.1

-
I’d say we need more transparency on some 'invisible' operations.
E.g, like I noted below — I opened a file, never actually changes anything on canvas or panels, chose to Print it and changed the printer and some parameters.
The History doesn’t say anything about the change, I can’t undo it, but it’s there when I quit. This is not exactly clear (and the change happens on a document level).But again, adding an asset IS a visible operation, it’s there in the History and you can undo it and see what has changed.
Assets ARE content, same as brushes, swatches, styles, symbols, while Export As doesn’t create any content (and the change happens at the app level). All is fair here, as I see it.
Let’s see if anybody else find it unfair. -
onenower commented
This state should be distinguished from changes in document content.
Otherwise, it is easy to mistakenly believe that the document content has changed something.
Before saving, it is necessary to repeatedly confirm whether the document content has changed. -
It’s a different approach actually. Collecting for Export creates an asset. Assets are like brushes, swatches, styles, it can be further edited, reused. Creating these ARE changes. Ai honors them.
A similar thing happens if you open a Print dialog, alter the settings, and then click Done button — these settings are considered to be changes for the document. Fair as well.
There is bug report even about not saving some changes like this in text styles: http://illustrator.uservoice.com/forums/601447/suggestions/47748554Export As doesn’t create assets, and the sticky changes the dialog offers don’t really belong to the document, but the app.
-
onenower commented
I think this approach is the same as' exporting as', except that the resources are exported as a form rather than the document itself changing, which can easily lead people to misunderstand whether I have accidentally made any changes.
-
Why do you think this is a bug though?
When you collect something as assets, these get stored within Asset Export panel, as assets — as user data. And user data added into a document IS a change. And in most cases this is something people can spend a lot of time to setup.
So why do you think it should be ignored and assets should not get saved?