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 DEBIAN

install-xpi

INSTALL-XPI(1)						     mozilla-devscripts suite						    INSTALL-XPI(1)

NAME

       install-xpi - installs a xpi file into a Debian package

SYNOPSIS

       install-xpi [options] xpi-file

DESCRIPTION

       install-xpi  is	a  helper  tool  for  packaging  XUL extensions. It installs the given xpi file into the correct directory and creates the
       required links based on the data in the install.rdf file.  It corrects the file permissions unless --preserve-permissions is specified.

       install-xpi will create a configuration file in /etc if the XUL extension provides one or more preferences files  in  defaults/preferences.
       The  configuration  file contains only a description where to find the overridable preferences.	debian/package.js is used as configuration
       file instead if it exists. The placeholder @INSTALLDIR@ is replaces by the actual installation directory. You can disable the creation of a
       system configuration file with --disable-system-prefs.

OPTIONS

       --disable-system-prefs
	      Do not create a system preference file in /etc.

       -x file, --exclude=file
	      The specified file from the xpi file will not be installed. You can use this parameter several times.

       -h, --help
	      Display a brief help message.

       -i directory, --install-dir=directory
	      The xpi file will be installed in the specified directory.  directory must be an absolute path. Use this parameter with care.

       -l directory, --link=directory
	      An  additional  link  from  the directory to the installation directory of the extension will be created. You can use this parameter
	      several times.

       -p package, --package=package
	      The xpi file will be installed in the specified binary package. If this parameter is not provided, the first binary  package  listed
	      in debian/control will be used.

       --preserve-permissions
	      The  permissions	of the files in the xpi file will not be modified. If this parameter is not provided, install-xpi will try to cor-
	      rect the permissions of the files to 644 (files that starts with a shebang will be corrected to 755).

       -r, --remove-license-files
	      Files with names like copying, licence, or license will not be installed.

       -v, --verbose
	      Print more information.

AUTHOR

       Benjamin Drung <bdrung@debian.org>

install-xpi							   January 2010 						    INSTALL-XPI(1)