Are you sure you want to quit Safari? Post: 303032397

Sponsored Content

Operating Systems OS X (Apple) Are you sure you want to quit Safari? Post 303032397 by Neo on Saturday 16th of March 2019 01:10:25 AM

03-16-2019

Administrator

Yeah, thanks.

I had a similar issue recently when my automatic 2AM scheduled shutdown of the MacPro happens with the Terminal app open. I would wake up and see the Mac was in "do you really want to quit the terminal" mode and not shut down (man, I hate that .. LOL), but I found a preferences option to avoid this problem.

Now, when testing web dev apps in Safari, especially on login and registration pages where there are passwords to save, Safari will also stop an automatic shutdown. That's annoying for sure.

This 12 core MacPro uses so much electricity and generates a lot of heat. I don't like it when it runs all night when sleeping, so auto shutdown is a great feature; but now Safari is blocking.

It's not a big deal.

The reason I am using Safari so much these days is that Safari always clears the Javascript cache out "completely" (when I quit and restart the browser) when I am testing live versions of the new CP. I noticed that Opera and Firefox are really troublesome at clearing out the JS cache, even when I quit the browser completely; and Chrome is better but not much. Safari is really great about this. FF and Opera the worst. Chrome is in between. I don't have time to figure out why; but I guess it's some user configuration switch in Chrome I am missing.

So, I develop on Chrome and test live on the web site with Safari to save time, and that is why I'm noticing all these Safari quirks.

After I get past this major Vue.js UserCP project, I'll use Safari less and I will not notice it again.

For those interested, all the Vue.js Javascript development in done on MacOS using node.js and node package manager (npm)).. and node.js is built on the amazing Google Chrome V8 Javascript engine; and so I think this is one reason why Chrome works so great with modern web apps, since almost all current state-of-the-art web apps are built using node.js and V8 is core.

Frankly as a developer, If I tried to develop (anything state-of-the-art) on Firefox or Opera, I would get very little done and be miserable, LOL. Those browsers are really falling behind in 2019 and I am quite sure their downward spiral will continue because Chrome is focused on modern web apps and Firefox is focused on "privacy" and seeming trying to block modern web apps. This is fight which FF will lose for sure with developers. Safari works fine. Opera, well, I open it from time to time, but never use it for anything "useful" from a web dev perspective.

Drifting off topic again......

Cheers.

Neo

View Public Profile for Neo

Visit Neo's homepage!

Find all posts by Neo

LEARN ABOUT MOJAVE

mac::apps::launch5.18

Launch(3)						User Contributed Perl Documentation						 Launch(3)

NAME

       Mac::Apps::Launch - Mac module to launch /quit applications

SYNOPSIS

	   use Mac::Apps::Launch;
	   my @apps = qw(R*ch Arch MPGP);
	   my $path = "HD:System Folder:Finder";
	   LaunchApps([@apps], 1) or warn $^E; # launch and switch to front
	   LaunchApps([@apps])	  or warn $^E; # launch and don't switch
	   LaunchApps($app, 1)	  or warn $^E; # launch and switch to front
	   LaunchSpecs($path, 1)  or warn $^E; # use path instead of app ID
	   QuitApps(@apps)	  or warn $^E; # quit all @apps
	   QuitAllApps(@apps)	  or warn $^E; # quit all except @apps
	   IsRunning('MACS');		       # returns boolean for whether
					       # given app ID is running
	   SetFront('MACS')	  or warn $^E; # set Finder to front
	   Hide('MACS') 	  or warn $^E; # hide Finder
	   Show('Finder', 1)	  or warn $^E; # show Finder (1 == use name)

DESCRIPTION

       Simply launch or quit applications by their creator ID.	The Finder can be quit in this way, though it cannot be launched in this way.

       This module is used by many other modules.

       This module as written does not work with MacPerls prior to 5.1.4r4.

       "Hide" and "Show" do not currently work on Mac OS X.

       Apps that don't have signatures under Mac OS X currently aren't handled, except with LaunchSpecs().

       "SetFront" and "IsRunning" can take a four-char creator ID ('MACS'), a bundle ID ('com.apple.Finder'), or a path
       (/System/Library/CoreServices/Finder.app).  They both optionally take a second parameter which affirms that the data is indeed a path (for
       those rare cases where a path might possibly look like a creator ID or bundle ID ... you never know).

       "IsRunning" will return the PSN of the application if it is running, which you can then use for targetting the app, or converting to a PID
       (with "Mac::Processes::GetProcessPID()"), to send signals to it.

EXPORT

       Exports functions "QuitApps", "QuitAllApps", and "LaunchApps", "IsRunning", "LaunchSpecs", "SetFront", "Hide", "Show".

AUTHOR

       Chris Nandor <pudge@pobox.com>, http://pudge.net/

       Copyright (c) 1999-2005 Chris Nandor.  All rights reserved.  This program is free software; you can redistribute it and/or modify it under
       the same terms as Perl itself.

perl v5.18.2							    2007-01-03								 Launch(3)