Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Safari is making me mad!
First killed the optional preference of ⌘+[0-9] of bookmark switching,
And now tab cycling is gone! :mad:

⌘ + [0-9] now seem to switch to the nth tab.

Tab cycling has always worked in El Cap for me using both of the original Safari 1.0 shortcuts:

⌘ + shift + [ or ] (prev/next) (i use this)
⌘ + shift + left arrow or right arrow (prev/next) (problem with this is it conflicts with text editing if box is active)
 
⌘ + [0-9] now seem to switch to the nth tab.

Tab cycling has always worked in El Cap for me using both of the original Safari 1.0 shortcuts:

⌘ + shift + [ or ] (prev/next) (i use this)
⌘ + shift + left arrow or right arrow (prev/next) (problem with this is it conflicts with text editing if box is active)

I always used these Tab-Switching shortcuts for any browser:
Ctrl+Tab
Ctrl+Shift+Tab

It works, no matter win/os x/linux/etc.

My main problem is ⌘ +[0-9] is also switching tabs!
In DP2 there was an option to choose ⌘ + [0-9] functionality but since DP3 it's gone.
 
Last edited:
I always used these Tab-Switching shortcuts for any browser:
Ctrl+Tab
Ctrl+Shift+Tab

It works, no matter win/os x/linux/etc.

My main problem is ⌘ +[0-9] is also switching tabs!
In DP2 there was an option to choose ⌘ + [0-9] functionality but since DP3 it's gone.
I read somewhere that Alt + ⌘ + [0-9] selects bookmarks. I'm still on Yosemite so can't check.
 
It appears that screen sharing as well as audio and video calls are not available in Messages anymore using .Mac/AIM account. The buddy list only gives you the button for initiating text chats. Here's a screenshot comparison between Mavericks and El Capitan (PB3):
Screen Shot 2015-08-04 at 20.29.22.pngScreen Shot 2015-08-04 at 20.48.43.png

Edit: looking at release notes, it looks like this is just beta weirdness. Thank goodness.
"AIM video chat and screen sharing in Messages are not available in this beta."
https://developer.apple.com/library/prerelease/mac/releasenotes/General/rn-osx-10.11/
 
The option to empty trash securely in Finder seems to be gone now, after early signs in the last beta. Instead you have the option to selectively delete files “immediately” from trash (I suppose that it is the same option).
Screen Shot 2015-08-04 at 20.09.52.png
Screen Shot 2015-08-04 at 20.11.21.png
Screen Shot 2015-08-04 at 20.11.40.png
 
The option to empty trash securely in Finder seems to be gone now, after early signs in the last beta. Instead you have the option to selectively delete files “immediately” from trash (I suppose that it is the same option).
View attachment 572999 View attachment 573001 View attachment 573002
As far as I understood, emptying trash securely wrote zeroes on top of the deleted files instead of just marking the files deleted – this was to make them impossible or at least significantly more difficult to recover from the disk. Do we know "delete immediately" does the same? The name of the feature doesn't imply that in any way, in my opinion.
 
  • Like
Reactions: sjinsjca
As far as I understood, emptying trash securely wrote zeroes on top of the deleted files instead of just marking the files deleted – this was to make them impossible or at least significantly more difficult to recover from the disk. Do we know "delete immediately" does the same? The name of the feature doesn't imply that in any way, in my opinion.

It has to, otherwise it is not deleted ‘immediately’. Nothing is ever deleted, just overwritten.
 
Not sure if this was present before El Capitan, but in pages when the cursor is over large white space it inverts.
ezgif-3181841673.gif
 
It has to, otherwise it is not deleted ‘immediately’. Nothing is ever deleted, just overwritten.
Not sure I follow. Emptying the trash normally, "non-securely", doesn't overwrite anything; the file system just marks the selected files deleted whilst the data itself is left intact. Secure deleting would overwrite the data, that's what the feature was for. "Delete immediately" just allows one to sort of selectively empty the trash. Searching around I can't find any evidence that would support the assumption that it actually overwrites the files it deletes, like Secure Empty did.

Edit: this obviously applies only to hard drives, which can write anywhere on the disk regardless of if there was prior data stored in that particular spot or not. Data on an SSD can't be overwritten, so writing new data goes into readily available empty memory cells. Occupied cells have to be individually purged first before new data can be written to them. The TRIM command tells the SSD to purge those cells after a file that resided in them is marked deleted.
 
Last edited:
Not sure I follow. Emptying the trash normally, "non-securely", doesn't overwrite anything; the file system just marks the selected files deleted whilst the data itself is left intact. Secure deleting would overwrite the data, that's what the feature was for. "Delete immediately" just allows one to sort of selectively empty the trash. Searching around I can't find any evidence that would support the assumption that it actually overwrites the files it deletes, like Secure Empty did.

Ah, I see what you are saying. You think the function just removes single items from trash but doesn’t do anything special? Good question. I don’t really see why that function would be necessary otherwise. Moreover, I can’t think that Apple would remove that function entirely. Maybe it behaves differently on encrypted versus non-encrypted drives?
 
As I understand it, however, secure deleting doesn't work particularly well on SSDs as the SSD controller manages the allocation of which block to use in writes (in order to evenly distribute 'wear' on the drive).
 
Ah, I see what you are saying. You think the function just removes single items from trash but doesn’t do anything special? Good question.
That's exactly what I meant.

As I understand it, however, secure deleting doesn't work particularly well on SSDs as the SSD controller manages the allocation of which block to use in writes (in order to evenly distribute 'wear' on the drive).
This is probably the reason why the function doesn't exist anymore. Majority of Macs sold these days ship with solid-state drives and support TRIM out of the box. The TRIM command tells the drive which blocks are no longer used and the drive will purge those at its leisure. In essence, the file will always be securely deleted, sooner or later.

Edit: perhaps someone can test if Secure Empty Trash is still available on a Mac with a hard drive? I doubt it's that smart but just an idea...
 
Apple seems to be getting rid of the name “rootless” now. Disk Utility makes no reference to it anymore, just System Integrity Protection. Same in the command-line utility “csrutil”.
Screen Shot 2015-08-04 at 21.32.04.png
Screen Shot 2015-08-04 at 21.36.51.png
 
  • Like
Reactions: Siannath and solid6
It has to, otherwise it is not deleted ‘immediately’. Nothing is ever deleted, just overwritten.
On ordinary HDDs but not on SSDs since they have write performance issues (it has to clear the cell first before it can write) the workaround is to clear out the cells earlier like when you delete stuff. Apple also removed the secure erase from the Disk Utility GUI but not from the commandline version. Might be that they are turning this into a pro version requiring the use of the commandline or a sign that they are moving towards things like Filevault and SSD (secure erase has (almost) no use in those cases).

The "secure empty trash" actually did more than just secure erase stuff. Sometimes items prevent the trash from emptying because they are in use for some reason. Using the "secure empty trash" get rid of every item in the trash no matter if it was in use or not. I'm hoping that simply emptying the trash now actually empties the trash. If not then we might have some issues (I can already see topics with "help, my trash doesn't empty" *sigh*).

Edit: as KALLT says in his post below this only goes for CoreStorage volumes which is now the default (it was before 10.11 so this is not new).
 
Last edited:
  • Like
Reactions: g-7
On ordinary HDDs but not on SSDs since they have write performance issues (it has to clear the cell first before it can write) the workaround is to clear out the cells earlier like when you delete stuff. Apple also removed the secure erase from the Disk Utility GUI but not from the commandline version. Might be that they are turning this into a pro version requiring the use of the commandline or a sign that they are moving towards things like Filevault and SSD (secure erase has (almost) no use in those cases).

The "secure empty trash" actually did more than just secure erase stuff. Sometimes items prevent the trash from emptying because they are in use for some reason. Using the "secure empty trash" get rid of every item in the trash no matter if it was in use or not. I'm hoping that simply emptying the trash now actually empties the trash. If not then we might have some issues (I can already see topics with "help, my trash doesn't empty" *sigh*).

One correction though: secure erase is still present in Disk Utility. It is merely not offered as an option for disks/partitions that are used as CoreStorage (anecdotal though). It is still offered for unencrypted Mac OS Extended (Journaled), for instance, and perhaps also for other file systems (I haven’t checked).

Both the Time Machine and External partition are Mac OS Extended (Journaled, Encrypted) and marked as CoreStorage. Snow Leopard is not encrypted.
Screen Shot 2015-08-04 at 22.44.11.png Screen Shot 2015-08-04 at 22.44.03.png Screen Shot 2015-08-04 at 22.43.42.png
 
Not sure if it is just me, but in the current beta when no messages are selected in Mail, the message preview pane is no longer translucent.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.