Possible bug with deleted stylesheet folders

[wheeleran]

New to Oxygen, building in a local environment, a Synology NAS on the same LAN. Using Oxygen 3.8 RC.

Description of the issue:
i contacted Oxygen Support asking them to identify the location of a code snippet attached to the bottom of the default universal.css file, which included my personal commenting syntax so i knew it was mine, which changed the Global container width of the site i was building. i had only one custom stylesheet, in Uncategorised, which did not include that code. but i recognised it. i had previously added it to another dummy stylesheet (ABC.css) in one of a series of dummy custom stylesheet folders (XYZ) while testing, then deleted a number of days ago. This code was active and working on my installation.

In searching for the cause, i had: deleted the Oxygen cache, re-signed shortcodes, re-saved permalinks, deleted browser cache, tested on other browsers, tested in incognito mode, restarted the machine, and tested on other machines. i had also deleted all custom stylesheets, then edited and re-saved universal.css, removing the code, but after saving and re-uploading, and creating a new blank stylesheet in Uncateogrised, the code re-appeared at the bottom of universal.css, though without any evidence of another custom folder OR stylesheet in the folder tree of Manage > Stylesheets.

Identifying the issue:
I created a new stylesheet folder, with the exact same name as the previous folder, XYZ. As prompted by Oxygen, i then created a new stylesheet in this folder (DEF.css) and saved it. In the XYZ folder tree, however, were two stylesheets: the newly created DEF.css, but also the initial ABC.css. i do not remember if i had deleted the stylesheet before deleting the folder, but my expectation would be that deleting the folder would delete it's contents.

Solving the issue:
Deleting the 'missing' code from the magically appearing ABC.css file solved my particular issue.

If my process is wrong, there is no core Oxygen documentation on working with custom stylesheets and folders.
Is this issue particular to me, or is it re-creatable on other installations and environments?

Thanks in advance.

[KittenCodes]

This has been reproduced and reported internally.