High Sierra behaves itself but Chrome doesn't
After holding back for a while I finally updated my iMac to High Sierra this week. I had read about various problems affecting some applications and, of course, the more recent security scare that has been patched in 10.13.2. The update went without a hitch, although it took a while. I think the file had downloaded some time previously, as no sooner I had updated than I received another update message to install the latest version, which also took a while.
In launchpad a few applications were marked with the symbol indicating that they were no longer compatible. Final Cut Express was one such, but this wasn't an issue as I had long since abandoned it in favour of Adobe's Premier Elements. There was an associated application, LiveType, which was also shown as non-compatible, but was equally of no interest to me. Adobe Bridge also had to go, but again I never used it. I had already upgraded to Office Home and Student 2016, expecting problems with my 2011 edition. Luminar prompted for an update, but having installed it I then decided to go for their Holidays' offer and upgraded to the 2018 version.
All seemed well until I updated one of my managed websites using RapidWeaver. I had a minor rendering problem in Safari. This resolved itself after clearing all caches but there was a fair bit of head-scratching before I got to that point. Firefox behaved impeccably but in Google Chrome the navigation symbols were showing visual artifacts. No amount of cache clearing or resetting would clear the problem, and having visited some forums it became clear that there are indeed some issues with Chrome when used with High Sierra. Having effectively given up on this particular problem I downloaded the still 'early adopters' version of Chrome Canary. I don't use Chrome generally and really only wanted to see if the issue persisted in this 'bleeding edge' version. I'm pleased to say it didn't. So for the time being anybody viewing the website using the original Chrome with High Sierra will experience this problem, but my hope is that the number of people in this category will be small.
The only other issue I experienced was with Word. I keep all my data on a network drive and when I attempted to close a document after saving, I received an error relating to permission to access the temporary file that Word had created. These files should be removed when the document is closed, but this wasn't happening. Again, it took a while to find out what was going on, but I eventually found an explanation that suggested that this was a problem associated with network drives with Word on High Sierra. The fix was to uncheck 'Save Autorecovery info' in Word, which of course disables auto-recovery, but it seems to have cured the irritating error messages and the orphan folders that were being created.
There may of course be other issues awaiting me as I use applications that I've not yet launched but, as they say, so far, so good!