> click on – everything (locally and remote) works – open local page works, but does not load embedded local images – open image in new tab – prompts ‘confirm the file to load and again’ – followed by a strange looping error Homepage loads upon startup local page, but does not display embedded local images I can reproduce the developer on/off difference and found more problems depending in the combination of developer on/off and local/non-local homepage: I have the same problem – Safari does no longer load local homepages. In every case, the issue was not in TCC/privacy/Mojave, but a bug in the app which was fixed quite quickly once the developers knew about it. I have now heard of several apps which try to use now-protected services or hardware but which don’t generate the right consent dialogs. This is particularly the case with TCC/privacy. Many Apple staff are very keen to fix bugs and really glad to work with us to report and fix them. This was on a Mojave beta, and it was a pretty serious issue, but I was very impressed. With TCC/privacy, it is totally different: within a couple of hours of reporting the bug, I was informed that the engineers were working on it, and it was fixed within a day or two. I have never been particularly diligent at reporting bugs to Apple, as they too often end up marked as duplicates and that’s the last that you hear of them. If you find bugs, report them first to the app developer (if the issue is with the app), and then to Apple. Regarding TCC and privacy, I must beg to differ. Yours-in-love-with-Apple-really-but-annoyed-at-them-thinking-they’re-my-mum-or-whatever But half-implementing a new protective policy that doesn’t properly ask permission when things go wrong – and breaks things without telling you – is yet another Apple decision that pleases neither the hacky-programmy-experty folks nor protects the average user when they get flustered that some art program is asking permission to delete something, god it might delete everything! Throw a bag over it and hope it goes away! I know the argument – makes things more foolproof, stops programs breaking things, virus, malware etc. MacOS has asked once for permission for Photoshop to delete a file, when in that program’s file menu I did such a heinous thing. The rubbish-but-the-only-thing-that-works solution? Just give any program that plays up full disk access and accessibility… er access. No errors or messages asking me to allow x or y popped up therefore it was decided, by someone somewhere, no that won’t work – you can run it, it can think it’s working but it’ll have no effect, give no errors and just annoy you as you reset the PRAM, restart, log on and off again. Lots of things, like CDock, ran but didn’t work. The odd thing is, as you say, go to a website, quit totally out of Safari, run it afresh again and it doesn’t give an error.Īs for Safari 12 / Mojave, it worked better than Sierra or High Sierra out of the (metaphorical) box but as someone who has customized the UI, written his own scripts, bits of code and extensions for that, and does a lot of development-type stuff, it’s been a pain working through the undocumented minefield of giving programs permission to do stuff like access the disk etc. A proxy error was the diagnosis – well, I don’t have a proxy, never have and after an unproductive afternoon down that minehole I decided to leave it. As usual, getting the right form of words is especially tricky for an issue like this – ‘safari 12 error locally stored home page’ certainly didn’t work when I tried it – and the error message/number, again something you’d think was easy to find info about, isn’t. Do you agree?Īt last, someone else reporting this problem! I’ve been having it since day one, and there seemed nothing from searching for answers. Other than pointing Safari at the file for my new Home page, I have made no other relevant changes in its settings. Once I have loaded another page in Sierra, and I go back to my Home page, those errors vanish, and it then loads as expected. Now, when I open Safari the following message appears:įollowed by another error page reporting that the error page couldn’t be found: I thought that something might have gone wrong with that file, although it could be opened in Safari perfectly well, and in any case wanted a blank black Home page instead. When I upgraded to Mojave 10.14 and fired up Safari for the first time, it threw an error. This is not the case for the Sierra variant of Safari 12.0.įor many years, my browser Home page has been a local HTML file, which I keep at the top level of my Home folder. It’s not a big deal, but a daily irritant: the Mojave variant of Safari 12.0 (14606.1.36.1.9) is unable to open a local Home page when it first opens.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |