If a custom file engine is used to make an archive file (e.g tar, zip, app specific format) appear as a directory, this may be broken in 4.8
The reason is that cached information from the filesystem is trusted to determine the filesystem object type.
In 4.7 there was no caching and a QFileInfo was constructed each time, which was responsible for poor performance.
As 4.8 is aware of whether custom file engines are in use or not, this can be fixed while only significantly affecting performance for applications that use them
App level workaround may be possible if the custom file engine takes ownership of the directory containing its mount point and overrides the begin/end/entryList functions.
This only covers the use case of archive files in an application owned directory, not the general case of anywhere in the file system.