Is there a way to apply styles to Safari only?
Asked Answered
M

24

288

I'm trying to find a way to apply CSS just to Safari, but everything I find also applies to Chrome. I know these are currently both WebKit browsers, but I'm having problems with div alignments in Chrome and Safari; each displays differently.

I have been trying to use this but it affects Chrome as well:

@media screen and (-webkit-min-device-pixel-ratio:0) { 
  #safari { display: block; } 
} 

Does anyone know of another one that will just apply to Safari?

Madson answered 2/5, 2013 at 22:4 Comment(6)
Not using CSS, you'll need to use javascript. https://mcmap.net/q/48064/-detect-safari-using-jquerySilicosis
I’d be more interested in the actual problem than a fragile and hacky solution. Is it (still) available somewhere?Surprint
For people who are posting 'does not work' - please realize that you need to know the version of Safari you are testing. There is no 'catch-all' Safari solution for every version. You need to provide that information with your posting or no-one can assist you in finding a solution.Albertinaalbertine
Different versions of Safari have different needs - check here for live examples: browserstrangeness.bitbucket.io/css_hacks.html#safari [Or the Mirror] browserstrangeness.github.io/css_hacks.html#safariAlbertinaalbertine
N.B. The question states: "i know these [Safari and Chrome] are both webkit browsers" But in April 2013, just before this question was asked, Google Chrome Browser switched from WebKit to Blink, a fork of WebKit.Holliman
Closing as not reproducible since Chrome uses Blink now, and did so basically since the time the question was asked.Clotilda
A
523
  • UPDATED FOR SONOMA & SAFARI 17.0 (Fall 2023 Update) *

PLEASE PLEASE -- If you are having trouble, and really want to get help or help others by posting a comment about it, Post Your Browser and Device (MacBook/IPad/etc... with both browser and OS version numbers!)

Claiming none of these work is not accurate (and actually not even possible.) Many of these are not really 'hacks' but code built into versions of Safari by Apple. More info is needed. I love the fact that you came here, and really want things to work out for you.

If you have issues getting something from here working on your site, please do check the test site via links below -- If a hack is working there, but not on your site, the hack is not the issue - there is something else happening with your site, often just a CSS conflict as mentioned below, or perhaps nothing is working but you may be unaware that you are not actually using Safari at all. Remember that this info is here to help people with (hopefully) short term issues.

The test site:

https://browserstrangeness.bitbucket.io/css_hacks.html#safari

AND MIRROR!

https://browserstrangeness.github.io/css_hacks.html#safari

NOTE: Filters and compilers (such as the SASS engine) expect standard 'cross-browser' code -- NOT CSS hacks like these which means they will rewrite, destroy or remove the hacks since that is not what hacks do. Much of this is non-standard code that has been painstakingly crafted to target single browser versions only and cannot work if they are altered. If you wish to use it with those, you must load your chosen CSS hack AFTER any filter or compiler. This may seem like a given but there has been a lot of confusion among people who do not realize that they are undoing a hack by running it through such software which was not designed for this purpose.

Safari has changed since version 6.1, as many have noticed.

Please note: if you are using Chrome [and now also Firefox] on iOS (at least in iOS versions 6.1 and newer) and you wonder why none of the hacks seem to be separating Chrome from Safari, it is because the iOS version of Chrome is using the Safari engine. It uses Safari hacks not the Chrome ones. More about that here: https://allthingsd.com/20120628/googles-chrome-for-ios-is-more-like-a-chrome-plated-apple/ Firefox for iOS was released in Fall 2015. It also responds to the Safari Hacks, but none of the Firefox ones, same as iOS Chrome.

ALSO: If you have tried one or more of the hacks and have trouble getting them to work, please post sample code (better yet a test page) - the hack you are attempting, and what browser(s) (exact version!) you are using as well as the device you are using. Without that additional information, it is impossible for me or anyone else here to assist you.

Often it is a simple fix or a missing semicolon. With CSS it is usually that or a problem of which order the code is listed in the style sheets, if not just CSS errors. Please do test the hacks here on the test site. If it works there, that means the hack really is working for your setup, but it is something else that needs to be resolved. People here really do love to help, or at least point you in the right direction.

That out of the way here are hacks for you to use for more recent versions of Safari.

You should try this one first as it covers current Safari versions and is pure-Safari only:

This one still works properly with Safari 17.0 (Fall-2023):

/* Safari 7.1+ */

_::-webkit-full-page-media, _:future, :root .safari_only {

  color:#0000FF; 
  background-color:#CCCCCC; 

}

To cover more versions, 6.1 and up, at this time you have to use the next pair of css hacks. The one for 6.1-10.0 to go with one that handles 10.1 and up.

So then -- here is one I worked out for Safari 10.1+:

The double media query is important here, don't remove it.

/* Safari 10.1+ */

@media not all and (min-resolution:.001dpcm) { @media {

    .safari_only { 

        color:#0000FF; 
        background-color:#CCCCCC; 

    }
}}

Try this one if SCSS or other tool set has trouble with the nested media query:

/* Safari 10.1+ (alternate method) */

@media not all and (min-resolution:.001dpcm)
{ @supports (-webkit-appearance:none) {

    .safari_only { 

        color:#0000FF; 
        background-color:#CCCCCC; 

    }
}}

This next one works for 6.1-10.0 but not 10.1 (Late March 2017 update)

This hack I created over many months of testing and experimentation by combining multiple other hacks.

NOTES: like above, the double media query is NOT an accident -- it rules out many older browsers that cannot handle media query nesting. -- The missing space after one of the 'and's is important as well. This is after all, a hack... and the only one that works for 6.1 and all newer Safari versions at this time. Also be aware as listed in the comments below, the hack is non-standard css and must be applied AFTER a filter. Filters such as SASS engines will rewrite/undo or completely remove it outright.

As mentioned above, please check my test page to see it working as-is (without modification!)

And here is the code:

/* Safari 6.1-10.0 (not 10.1) */

@media screen and (min-color-index:0) and(-webkit-min-device-pixel-ratio:0) 
{ @media {
    .safari_only { 

        color:#0000FF; 
        background-color:#CCCCCC; 

    }
}}

For more 'version specific' Safari CSS, please continue to read below.

/* Safari 11+ */

@media not all and (min-resolution:.001dpcm)
{ @supports (-webkit-appearance:none) and (stroke-color:transparent) {

    .safari_only { 

        color:#0000FF; 
        background-color:#CCCCCC; 

    }
}}

One for Safari 11.0:

/* Safari 11.0 (not 11.1) */

html >> * .safari_only {

  color:#0000FF; 
  background-color:#CCCCCC; 

}

One for Safari 10.0:

/* Safari 10.0 (not 10.1) */

_::-webkit-:host:not(:root:root), .safari_only {

  color:#0000FF; 
  background-color:#CCCCCC; 

}

Slightly modified works for 10.1 (only):

/* Safari 10.1 */

@media not all and (min-resolution:.001dpcm)
{ @supports (-webkit-appearance:none) and (not (stroke-color:transparent)) {

    .safari_only { 

        color:#0000FF; 
        background-color:#CCCCCC; 

    }
}}

Safari 10.0 (Non-iOS Devices):

/* Safari 10.0 (not 10.1) but not on iOS */

_::-webkit-:-webkit-full-screen:host:not(:root:root), .safari_only {

  color:#0000FF; 
  background-color:#CCCCCC; 

}

Safari 9 CSS Hacks:

A simple supports feature query hack for Safari 9.0 and up:

@supports (-webkit-hyphens:none)
{

  .safari_only {
    color:#0000FF; 
    background-color:#CCCCCC; 
  }

}

A simple underscore hack for Safari 9.0 and up:

_:not(a,b), .safari_only {

  color:#0000FF; 
  background-color:#CCCCCC; 

}

Another one for Safari 9.0 and up:

/* Safari 9+ */

_:default:not(:root:root), .safari_only {

  color:#0000FF; 
  background-color:#CCCCCC; 

}

and another support features query too:

/* Safari 9+, < 13.1 */

@supports (-webkit-marquee-repetition:infinite) and (object-fit:fill) {

    .safari_only { 

        color:#0000FF; 
        background-color:#CCCCCC; 

    }
}

One for Safari 9.0-10.0:

/* Safari 9.0-10.0 (not 10.1) */

_::-webkit-:not(:root:root), .safari_only {

  color:#0000FF; 
  background-color:#CCCCCC; 

}

Safari 9 now includes feature detection so we can use that now...

/* Safari 9 */

@supports (overflow:-webkit-marquee) and (justify-content:inherit) 
{

  .safari_only {
    color:#0000FF; 
    background-color:#CCCCCC; 
  }

}

Now to target iOS devices only. As mentioned above, since Chrome on iOS is rooted in Safari, it of course hits that one as well.

/* Safari 9.0 (iOS Only) */

@supports (-webkit-text-size-adjust:none) and (not (-ms-ime-align:auto))
and (not (-moz-appearance:none))
{

  .safari_only {
    color:#0000FF; 
    background-color:#CCCCCC; 
  }

}

one for Safari 9.0+ but not iOS devices:

/* Safari 9+ (non-iOS) */

_:default:not(:root:root), .safari_only {

  color:#0000FF; 
  background-color:#CCCCCC; 

}

And one for Safari 9.0-10.0 but not iOS devices:

/* Safari 9.0-10.0 (not 10.1) (non-iOS) */

_:-webkit-full-screen:not(:root:root), .safari_only {

  color:#0000FF; 
  background-color:#CCCCCC; 

}

Below are hacks that separate 6.1-7.0, and 7.1+ These also required a combination of multiple hacks in order to get the right result:

/* Safari 6.1-7.0 */

@media screen and (-webkit-min-device-pixel-ratio:0) and (min-color-index:0)
{  
   .safari_only {(;

      color:#0000FF; 
      background-color:#CCCCCC; 

    );}
}

Since I have pointed out the way to block iOS devices, here is the modified version of Safari 6.1+ hack that targets non-iOS devices:

/* Safari 6.1-10.0 (not 10.1) (non-iOS) */

@media screen and (min-color-index:0) and(-webkit-min-device-pixel-ratio:0) 
{ @media {
    _:-webkit-full-screen, .safari_only { 

        color:#0000FF; 
        background-color:#CCCCCC; 

    }
}}

To use them:

<div class="safari_only">This text will be Blue in Safari</div>

Usually [like in this question] the reason people ask about Safari hacks is mostly in reference to separating it from Google Chrome (again NOT iOS!) It may be important to post the alternative: how to target Chrome separately from Safari as well, so I am providing that for you here in case it is needed.

Here are the basics, again check my test page for lots of specific versions of Chrome, but these cover Chrome in general. Chrome is version 45, Dev and Canary versions are up to version 47 at this time.

My old media query combo I put on browserhacks still works just for Chrome 29+:

/* Chrome 29+ */

@media screen and (-webkit-min-device-pixel-ratio:0) and (min-resolution:.001dpcm)
{
    .chrome_only {

       color:#0000FF; 
       background-color:#CCCCCC; 

    }
}

An @supports feature query works well for Chrome 29+ as well... a modified version of the one we were using for Chrome 28+ below. Safari 9, the coming Firefox browsers, and the Microsoft Edge browser are not picked up with this one:

/* Chrome 29+ */

@supports (-webkit-appearance:none) and (not (overflow:-webkit-marquee))
and (not (-ms-ime-align:auto)) and (not (-moz-appearance:none))
{
    .chrome_only {

       color:#0000FF; 
       background-color:#CCCCCC; 

    }
}

Previously, Chrome 28 and newer were easy to target. This is one I sent to browserhacks after seeing it included within a block of other CSS code (not originally intended as a CSS hack) and realized what it does, so I extracted the relevant portion for our purposes:

[ NOTE: ] This older method below now pics up Safari 9 and the Microsoft Edge browser without the above update. The coming versions of Firefox and Microsoft Edge have added support for multiple -webkit- CSS codes in their programming, and both Edge and Safari 9 have added support for @supports feature detection. Chrome and Firefox included @supports previously.

/* Chrome 28+, Now Also Safari 9+, Firefox, and Microsoft Edge */

@supports (-webkit-appearance:none) 
{
    .chrome_and_safari {

       color:#0000FF; 
       background-color:#CCCCCC; 

    }
}

The block of Chrome versions 22-28 (If needed to support older versions) are also possible to target with a twist on my Safari combo hacks I posted above:

/* Chrome 22-28 */

@media screen and(-webkit-min-device-pixel-ratio:0)
{
    .chrome_only {-chrome-:only(;

       color:#0000FF; 
       background-color:#CCCCCC; 

    );}
}

NOTE: If you are new, change class name but leave this the same-> {-chrome-:only(;

Like the Safari CSS formatting hacks above, these can be used as follows:

<div class="chrome_only">This text will be Blue in Chrome</div>

So you don't have to search for it in this post, here is my live test page again:

https://browserstrangeness.bitbucket.io/css_hacks.html#safari

[Or the Mirror]

https://browserstrangeness.github.io/css_hacks.html#safari

The test page has many others as well, specifically version-based to further help you differentiate between Chrome and Safari, and also many hacks for Firefox, Microsoft Edge, and Internet Explorer web browsers.

NOTE: If something doesn't work for you, check the test page first, but provide example code and WHICH hack you are attempting for anyone to assist you.

Albertinaalbertine answered 22/9, 2014 at 13:23 Comment(51)
Just want to say that test page is awesome. I can now browse to that site with any device and see which css rules are applicable!Kurr
Will this apply to Safari on iPhone or iPad?Hither
I have an iPad mini, and it works on it. As long as you have Safari 6.1 or newer (8 is current) then you are good. So yes.Albertinaalbertine
actually, I just solved my own question using a combination of the example above AND the (;property: value;); below and it worked great!Siphon
The hack for Safari 6.1+ at the top of this answer throws an error in the Sass compiler. Is there a way to solve it?Laminous
@Laminous Sorry but you cannot compile or filter the hacks, it ruins them. They have to be used as-is. (Add them to the completed css file after compilation.) The fact that they are non-standard is why they work.Albertinaalbertine
a media query within a media query holy shoot :)Cohby
@Jeff Clayton, how do you use 6.1+ with certain screen size? I want the safari only css apply when screen size is at 768px. How to make that work?Indiscretion
The interior media query can be used for that. Instead of just media { css here } you can media screen and (min-width:768px) and (max-width:768px) { css here } leave the outer one as-is. The reason it works is the nested media queries only existed after Safari 6.0, but you can make it have any media effect you wish.Albertinaalbertine
This helped me fixed a really annoying Safari problem. Thank you so much! +1!Cathee
@MayankVadiya Please provide example code. Are you using all parts of the CSS code I provided? And what CSS/which CSS hack are you talking about? Usually when people have issues they are not using the entire hack as written. Please go to the test page and check the examples and see if they are not working on your machine. What browser(s) are you trying? Is the version of browser matching up to the browser you are using? Without any further information you cannot be assisted. Viewing the site you are working on would be the best way to get assistance here. Thanks in advance.Albertinaalbertine
@JeffClayton can talk in chatGnathous
@MayankVadiya you are invited to chat, invite sent css-hacks roomAlbertinaalbertine
Ah, I still may be able to help, are you attempting to filter or compile the hacks you are trying (which are you trying?) And have you looked at the test page to see if they work for you there? If so, what are you doing differently? If not, I would love to find out what is needed to update them.Albertinaalbertine
I trimmed up notes at the end on posting and asking for help.Albertinaalbertine
Thank you for this comprehensive list! There seems to be a typo in the first answer where @media is stated twice. Removing it allowed it to work for me!Decanal
@Decanal You are welcome but no that is not a typo, the double media query blocks many older browsers, you do need all of the closing brackets as well. What happens if you remove it is that additional browsers will be allowed that shouldn't be. Try redoing a copy of the hack in entirety on a fresh page, check my test page and I bet the test does work here: browserstrangeness.bitbucket.org/css_hacks.htmlAlbertinaalbertine
In my experience with the safari 6.1 hack, it has never failed and the only people who thought it has, had not copied all of the parts of it, or modified it before using it. It needs to be used exactly as written or it will not have the right results. Each person in the past contacted me back and let me know that it did work after they tried it again cleanly and in its complete form.Albertinaalbertine
@RobertoFlores did you look at the test site to see if it works on your browser first? Also, which version are you testing? Do you know which version of browser you are using? Usually that is the key. Also - there are several here. Could you provide a sample page? Perhaps I might be able to assist? Without any useful information or source code, I cannot help you. Thanks in advance.Albertinaalbertine
Scroll down to the bottom of the test page to match at least your browser's user agent string. Most likely it is a browser version that you are having trouble with. Otherwise, be sure you post the CSS hack or hacks after your style sheets are loaded, in their complete form and not through a css filtering program. That should fix your problem.Albertinaalbertine
Great solution, I had the same SASS compiler problem as @Blackbird, but as you say, compiler would probably break the spacing etc anyway, so I've added to the final output and works perfectlyCommix
Updated OSX Sierra last night, now hoping for another update?Tucket
Good catch, they did change things -- I just updated OS X to 10.12.4 and safari updated to version 10.1 (12603.1.30.0.34) with it -- this one works for 7.1+ still: _::-webkit-full-page-media, _:future, :root .selector { property:value; }Albertinaalbertine
@Tucket ok check it now and also the Safari section of the live test page reflecting the updated Safari stats.Albertinaalbertine
I can't get your first method (10.1) to work with a media query: @ media screen and (max-width: 767px) { _::-webkit-full-page-media, _:future, :root .flex-container { display: none; } } Works without the media query though. Any ideas?Baseline
-webkit-full-page-media may be at odds with your 'max size' media query wrapper - try setting your size to greater than the size of your monitor and seeing if you have different results for testing - I haven't found very many specific ones. You may have to use 2 (the 6.1-10 hack and the 10.1+ hack) as separate css blocks.see here: browserstrangeness.com/css_hacks.html#safariAlbertinaalbertine
@KyleVassella nest either hack inside your width query wrapper and that may do what you want.Albertinaalbertine
This one: @ media not all and (min-resolution:.001dpcm) { @ media { .selector { property:value; } } } you can actually add your max-width call to the interior blank media query instead of making it triple nestedAlbertinaalbertine
Between the two of them you would be able to cover your safari targets -- the other being this one: @ media screen and (min-color-index:0) and(-webkit-min-device-pixel-ratio:0) { @ media { .selector { property:value; } } }Albertinaalbertine
they don't overlap (safari 6.1-10.0) and (safari 10.1+) but they cannot be combined into one.Albertinaalbertine
at the very least a flexbox is not expected to be full page media so i can imagine that is inherently an issue with what you want to doAlbertinaalbertine
So are you suggesting it would help to be able to target browsers in CSS in case a browser needs specific attention? How would you design a style to handle that?Coxa
@1.21gigawatts -- Almost... this is meant to be temporary only until one can find a way to rewrite larger css rule sets to target specific browsers that are not acting properly with the code as it stands on a site that otherwise works properly. These code snippets do already target specific browsers, a way to place browser specific css in a style sheet, so not sure exactly what you are asking. If you have found examples in your own work where your css does not act the same way it should in all browsers, then you may already have the answer you are looking for.Albertinaalbertine
Would it be helpful if where you needed to you could declare styles that targeted the manufacturer and version? For example, if you needed to set styles specific to Chrome versions 10 to 11 you could say, --chrome-10-11-color: red or for Safari, --safari-color: blue? I have a use case now that I need to make adjustments for Edge. If I could say --edge-color: green in one line of CSS I would be done with the project. If later on Edge changes I can go back and change that line to --edge-upto-12-color: green.Coxa
@1.21gigawatts you can do that. There is no reason why you can't do it that way. Over time you may need to go back and check and see if a hack you chose (often a year or years later) has been picked up by another browser or removed from the one you are at the current time targeting.Albertinaalbertine
@JeffClayton What do you mean? The browser isn't aware of these styles or how to apply them. Parsing browser specific styles would have to be implemented by browser manufacturers. For example, I just typed -safari-line-height:1 and -webkit-line-height:1 in Safari and neither were applied.Coxa
Here is an example using one from my test page: First set a default color in css (you already have this) color:black; Set a css variable color called --safari-11-up-color: blue; In the css later do this: @ media not all and (min-resolution:.001dpcm) { @ supports (-webkit-appearance:none) and (stroke-color:transparent) { body { color: var(--safari-11-up-color); } } }Albertinaalbertine
[note that in the css code I just posted I had to separate the @ symbols from the media and supports queries it should be ATmedia not AT(space)media in this comment block.]Albertinaalbertine
So if you try that you will have different hacks, with specific variables tailored to each css hack within them, but listed above as pre-defined variables.Albertinaalbertine
If you go to my test page and view source, while I didn't generally use css variables, I did use a naming scheme like this for a good portion of my css styles.Albertinaalbertine
@1.21gigawatts it just takes a different method -- you can't really create new 'named' properties as you are correct, the browser does not know them. But you can set them to variables with names you choose in order to do a similar effect.Albertinaalbertine
The reason you did not understand me is that you did not realize that the code you asked me about previously, --safari-color: blue is valid but NOT the same as -safari-color: blue. The double dash is doable because it is a a reference to a definable css variable... NOT a browser property. The question you asked me later is the single dash, which would refer to a property not a variable. So really you didn't actually say the same thing in your question that you said in the test you just showed me. Look up how to use CSS variables for more information.Albertinaalbertine
@FairyQueen - please check the demo site to be sure none of them are working for you. Figure out which version of the browser you are using as well to decide which may match. Odds are one of them does. If it is not working within your own CSS, it is not the hack that is the issue, but something else. Other than that, you need to provide more information (like browser version and maybe OS version) if you need some assistance.Albertinaalbertine
Perhaps provide a link to a page where one of these hacks is attempted and someone may be able to resolve it. Please do check one of my browserstrangeness pages though to see these Safari hacks live. More than one often works. Knowing if you are using iOS or Desktop version with Safari may be important for others to assist you as well. So far, there has always been an ordering issue or a different css code interfering with it, or an incomplete or otherwise damaged copy of a hack (which cannot work as intended.)Albertinaalbertine
Simply, more information is needed if you have the odd chance that none of the ones on the test sites are working for you. Please read my notes at the top pertaining to help requests in order to receive any further assistance.Albertinaalbertine
this is absurd complications for todays times, too much clutter and bs, there should be onliner..Pumpernickel
@Pumpernickel I understand your frustration here. There are a few if you look for specific versions. This was not easy to accomplish due to the fact that they are not provided via standards. If you choose one for Safari 7.1+ or Safari 9+ you cover most of the current versions. However, one of the reasons one chooses a hack is because one version may not act like another, meaning your reasoning is not the ONLY reason one needs a hack. So the same hack does not suffice.Albertinaalbertine
The 7.1+ css solution didn't work. It didn't turn any text blue.Sg
@Sg - please verify me 2 things: what specific version of Safari are you using, and if you don't see it turn red here (the top hack on the page) at my test site: browserstrangeness.bitbucket.io/css_hacks.html (your comment needs more information to validate and update the hack notes)Albertinaalbertine
For anyone posting comments like these 'did not work,' especially people newer to css issues, please first go to my test site and see if the hack works there. If it does not, please post your specific os version like 'os x 10.12.1' and your exact browser version (not just 'safari,' but 'safari 9.0' for example) or nobody can help diagnose the issue. If it works on my site and not yours, that means you have a difference in your html/css that needs to be resolved. I hope that helps.Albertinaalbertine
This is awesome, thanks so much for sharing. And I confirm the Safari 10.1+: hack STILL WORKS PERFECTLY as of NOVEMBER 11 2020 cheersBlastopore
C
94

There is a way to filter Safari 5+ from Chrome:

@media screen and (-webkit-min-device-pixel-ratio:0) { 
    /* Safari and Chrome */
    .myClass {
     color:red;
    }

    /* Safari only override */
    ::i-block-chrome,.myClass {
     color:blue;
    }
}
Continuation answered 4/7, 2013 at 14:2 Comment(5)
jeffclayton.wordpress.com/2014/07/22/… - I have been working on many (I test and create css hacks for browserhacks.com) and test page here: browserstrangeness.bitbucket.org/css_hacks.html#webkitAlbertinaalbertine
Note: in iOS [tested in iOS 7], the chrome version is actually running the safari engine, so on ipads or iphones, you use the safari hacks. For other devices, they are different.Albertinaalbertine
So, basically the code in the answer works for Safari 5.0 and 6.0 and not 6.1+?Ornelas
To be absolutely accurate, the ::i-block-chrome, .myClass { } construct allows only Safari 5.1-6.0, but also Chrome 10-24 (old version of Chrome not really used anymore so not entirely worth mentioning) but nothing newer - Safari hacks tend to work like that: one batch handles 5.1-6.0, another handles 6.1-7.0, and the newer ones handle 7.1-8.0. They seem to update things a lot until they decide to go to the next numerical version which is very close to the previous '.1' release.Albertinaalbertine
At the time of this answer in 2013, Safari 6.1 had just been released, so not enough people had seen that the browser had changed so this was the most accurate one at the time. If you need newer ones check my answer below. This was a great answer at the time it was provided. Time changes however so I posted my work as an update to this one. It took months for me to create the 6.1-7.0 and 7.1-8.0 ones. I hope you like the results. Most likely when a version 8.1 is released if it follows the pattern, it will also require a different hack. Again only time will tell.Albertinaalbertine
A
21

Sarari Only

.yourClass:not(:root:root){ 
    /* ^_^ */ 
}
Admonition answered 30/5, 2014 at 7:0 Comment(9)
Care to add some explanation? Do I literally type root:root?Esta
This one is exactly correct for Safari 3.x (and Chrome version 1.0 only though nobody uses Chrome 1.0 since it is in the 30's now...)Albertinaalbertine
This one now targets Safari 9.0 as well, so complete stats have updated: /* Chrome 1.0, Safari 3.X, Safari 9.0+ */Albertinaalbertine
Works for the Safari 9.1.1!Oleviaolfaction
The :not(:root:root) selector is invalid according to CSS Selectors 3 spec (in which :not() can contain only a simple selector, i.e. one type selector or one ID or one class or one pseudo-class), but completely valid according to CSS Selectors 4 (where :not() accepts list of selectors). It's true that currently only Safari understands CSS Selectors 4 syntax, but this solution is not future-proof.Planogamete
Very few hacks are not (and much actual standard code is not due to version changes) future proof. The best plan is if you are going to use a css hack, use it only as a temporary fix in order to buy time to make a more official cross-browser update.Albertinaalbertine
The reason some of these hacks work is because they are not standard, and are rendered strangely. The :root:root combo works because other browsers filter it out as bad css. Hence... hack.Albertinaalbertine
This affect chrome tooEnvelopment
This no longer works unfortunatelyWinifred
J
21

Works on iOS 16 and macOS Ventura:

@supports (font: -apple-system-body) and (-webkit-appearance: none) {
  .body {
    background-color: red;
  }
}
Jeanene answered 9/11, 2022 at 20:53 Comment(2)
I really like this suggestion, because it's self-documenting and the very future proof. An "apple" font is very likely is only available in Safari now and for a long time to come...Spitz
@Spitz Yeah, same thought here, even... do you think we could 'get away' just with the font: -apple-system-body part?Pulque
I
14

This hack 100% work only for safari 5.1-6.0. I've just tested it with success.

@media only screen and (-webkit-min-device-pixel-ratio: 1) {
     ::i-block-chrome, .yourcssrule {
        your css property
    }
}
Indigent answered 22/1, 2015 at 15:50 Comment(2)
This hack is actually for both Chrome and Safari in different versions. It allows Chrome 10-24 (which nobody uses any more which is why people listed that it blocked Chrome) and Safari 5.1-6.0 only. It does not work for Safari 6.1 and newer however. At the time there was no better hack of its kind.Albertinaalbertine
People - please be careful. What these comments are describing is a method that does not work for versions of Safari in the last several years and only works for old versions. What that really means is that most people on the internet will not have the result you are looking for, but only people with older computers. This does not work for current operating systems. At this time most people have version 12 and higher (not 6.0 and lower, which were current only during the windows XP era.)Albertinaalbertine
W
10

When using this safari-only filter I could target Safari (iOS and Mac), but exclude Chrome (and other browsers):

@supports (-webkit-backdrop-filter: blur(1px)) {
  .safari-only {
    background-color: rgb(76,80,84);
  }
}
Wessels answered 12/9, 2019 at 8:58 Comment(3)
this doesn't filter EdgeSg
From all the hacks in this page, this is the only one that worked for me. It filtered Firefox, Chrom, Opera and Edge on Mac in 2022.Romantic
Confirmed to filter Apple Safari on MacBook vs. Chrome on my Linux PC in April 2023. Hopefully I don't need to care about any other edge cases.Depolymerize
A
7

For those who want to implement a hack for Safari 7.0 and below, but not 7.1 and above -- use:

.myclass { (;property: value;); }
.myclass { [;property: value;]; }
Amandy answered 13/6, 2014 at 6:52 Comment(5)
I gave this a try on Safari 7 and couldn't get it to work. Can you provide a working example by any chance?Goblet
@Juicy: There are live tests of these at browserhacks.com -- They work on Safari 7 and lower, and also Chrome 28 and lower. (As mentioned in another posting iOS 7 and 8 maybe others as well use the Safari engine for Chrome, so Chrome and Safari on iPads are both really Safari)Albertinaalbertine
You may have been trying it in Safari 7.1, not Safari 7.0. It is valid for 7.0 and earlier, not 7.1 and newer. When this answer was posted, 7.0 was the latest version of Safari so it was true at that time.Albertinaalbertine
works for Safari for Windows (version 5.1.7 (7534.57.2))Lade
works for Safari for Mac (Version 6.0.2 (7536.26.17))Fishy
L
6

Replace your class in (.myClass)

/* Safari only */ .myClass:not(:root:root) { enter code here }

Loadstone answered 12/7, 2016 at 12:41 Comment(4)
This is a good one for Safari -- the only other browser it targets is Chrome 1 (nobody uses Chome 1 anymore)Albertinaalbertine
Exact Specs for people who are not using the latest Macs: Chrome 1, Safari 3.X, Safari 9.0+ (not Safari 4-8)Albertinaalbertine
This works with the latest version of Safari 7+ and as far as I can tell should be the accepted answer.Understrapper
This no longer worksWinifred
T
6

I like to use the following method:

var isSafari = /Safari/.test(navigator.userAgent) && /Apple Computer/.test(navigator.vendor);
if (isSafari) { 
  $('head').append('<link rel="stylesheet" type="text/css" href="path/to/safari.css">') 
};
Telluride answered 20/6, 2017 at 21:0 Comment(2)
This JavaScript hack method requires the JQuery package to be installed.Albertinaalbertine
This is regarded as extremely bad practice, browser sniffing is very error-prone and leads to heaps of false positives. Don't do this, even media-query sniffing is very dirty but could be acceptable for very small changes.Peppergrass
K
4

By the way, for any of you guys that just need to target Safari on mobiles, just add a media query to this hack:

@media screen and (max-width: 767px) {
    _::-webkit-full-page-media, _:future, :root .safari_only {
        padding: 10px; //or any property you need
    }
}

And don't forget to add the .safari_only class to the element you want to target, example:

<div class='safari_only'> This div will have a padding:10px in a mobile with Safari  </div>
Kantianism answered 31/3, 2017 at 20:35 Comment(0)
I
4

This works:

@media not all and (min-resolution:.001dpcm) { 
  @media {
    /* your code for Safari Desktop & Mobile */
    body {
      background-color: red;
      color: blue;
    }
    /* end */
  }
}
Isagoge answered 5/12, 2018 at 18:48 Comment(2)
@heLL0 because dcpm unit is not supported by Safari at all (@media not all and...) caniuse.com/mdn-css_types_resolution_dpcmPallaten
I've been trying dozens of @media queries to target iOS Safari Mobile but not Firefox Desktop - this is the first one I've come across that has worked. Thank you.Holliman
E
4

https://www.bram.us/2021/06/23/css-at-supports-rules-to-target-only-firefox-safari-chromium/#safari

@supports (background: -webkit-named-image(i)) {
// 
}

h1::after {
  content: "No";
  margin-left: .3em;
  color: red;
}

@supports (background: -webkit-named-image(i)) {
  h1::after {
    content: "Yes";
    color: green;
  }
}
<!DOCTYPE html>
<html>
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width">
  <title>JS Bin</title>
</head>
<body>
  
  <h1>Safari?</h1>

</body>
</html>
Eigenfunction answered 7/12, 2022 at 23:37 Comment(0)
J
3

Note: If iOS-only is sufficient (if you're willing to sacrifice Safari desktop), then this works:

    @supports (-webkit-overflow-scrolling: touch) {
    /* CSS specific to iOS devices */ 
    }
Jayme answered 11/9, 2019 at 16:16 Comment(0)
S
2

hi i ve made this and it worked for me

@media(max-width: 1920px){
    @media not all and (min-resolution:.001dpcm) {

        .photo_row2 {
            margin-left: 5.5% !important;
        }
    }
}

@media(max-width: 1680px){
    @media not all and (min-resolution:.001dpcm) {

        .photo_row2 {
            margin-left: 15% !important;
        }

    }
}

@media(max-width: 1600px){
    @media not all and (min-resolution:.001dpcm) {

        .photo_row2 {
            margin-left: 18% !important;
        }

    }
}


@media (max-width: 1440px) {
@media not all and (min-resolution:.001dpcm) {

        .photo_row2 {
            margin-left: 24.5% !important;
        }

    }

}


@media (max-width: 1024px) {
@media not all and (min-resolution:.001dpcm) {
    @media {
        .photo_row2 {
            margin-left: -11% !important;
        }

    }

}
Slav answered 30/3, 2018 at 8:49 Comment(1)
This is a nice set, good use of the hack with multiple device settings for web sites using responsive views.Albertinaalbertine
A
2

If you are looking Safari specific browser hack

I tried this, and it's working for me (only for Safari)

@supports (-webkit-hyphens:none){
        @content
}
    
@media not all and (min-resolution:.001dpcm)
    { @supports (-webkit-appearance:none) and (stroke-color:transparent) {
            @content
    }
}
Airglow answered 24/3, 2022 at 8:19 Comment(0)
L
1

You can use a media-query hack to select Safari 6.1-7.0 from other browsers.

@media \\0 screen {}

Disclaimer: This hack also targets old Chrome versions (before July 2013).

Leisha answered 7/1, 2016 at 15:0 Comment(1)
It doesn't work on newer Safari, the stats for this one are surgical however: Safari 6.1-7.0, Chrome 22-28 so still handy.Albertinaalbertine
H
1

Step 1: use https://modernizr.com/

Step 2: use the html class .regions to select only Safari

a { color: blue; }
html.regions a { color: green; }

Modernizr will add html classes to the DOM based on what the current browser supports. Safari supports regions http://caniuse.com/#feat=css-regions whereas other browsers do not (yet anyway). This method is also very effective in selecting different versions of IE. May the force be with you.

Handily answered 25/1, 2016 at 17:21 Comment(4)
modernizr is a great javascript addon to websites to identify browsers, excellent tool! -- this hack will work (as others) until other browsers decide to support the regions featureAlbertinaalbertine
CSS regions is not supported anymore.Anneliese
Regions enables me to target Safari 6.1 to 11 and 7.1 to 11.2 on iOS and that alone is great already.Hospice
@Hospice - great posting your stats on this, hacks are only good as the knowledge of what browsers they target.Albertinaalbertine
S
1

At the end I use a little JavaScript to achieve it:

if (navigator.vendor.startsWith('Apple'))
    document.documentElement.classList.add('on-apple');

then in my CSS to target Apple browser engine the selector will be:

.on-apple .my-class{
    ...
}
Smukler answered 6/2, 2019 at 21:53 Comment(0)
P
1

It works in from 10 to 16 IOS version:

@supports (-webkit-hyphens:none){ 
    ...
}
Pincushion answered 11/9, 2023 at 16:36 Comment(0)
P
0

Wordpress solution:

<?php
add_filter( 'body_class', 'browser_body_class' );

function browser_body_class( $classes ) {
    global $is_lynx, $is_gecko, $is_IE, $is_opera, $is_NS4, $is_safari, $is_chrome, $is_iphone;

    if( $is_lynx ) $classes[]       = 'lynx';
    elseif( $is_gecko ) $classes[]  = 'gecko';
    elseif( $is_opera ) $classes[]  = 'opera';
    elseif( $is_NS4 ) $classes[]    = 'ns4';
    elseif( $is_safari ) $classes[] = 'safari';
    elseif( $is_chrome ) $classes[] = 'chrome';
    elseif( $is_IE ) $classes[]     = 'ie';
    else $classes[] = 'unknown';

    if( $is_iphone ) $classes[] = 'iphone';
    return $classes;
}
?>
Planksheer answered 23/8, 2023 at 6:36 Comment(0)
C
0

...practically only for iSF3.2+(mSF4+)

@media (-webkit-transition) {/*CSS*/}

Why? https://developer.mozilla.org/en-US/docs/Web/CSS/@media/-webkit-transition


...only for iSF10.1+(mSF10.12.1+)

@supports (-webkit-appearance:-apple-pay-button) {/*CSS*/}

Why? https://developer.apple.com/documentation/apple_pay_on_the_web/displaying_apple_pay_buttons_using_css


...only for iSF9+

@supports (-webkit-touch-callout:none) {/*CSS*/}

Why? https://developer.mozilla.org/en-US/docs/Web/CSS/-webkit-touch-callout

See https://mcmap.net/q/48065/-css-media-query-to-target-only-ios-devices-duplicate

Circuitous answered 29/8, 2023 at 11:57 Comment(0)
C
0

Why not invert-detect apple pay? that's what we do:

@supports (not (-apple-pay-button-style: inherit)) {
.hide-apple-wallet-on-non-safari {
    display: none;
  }
}
Collagen answered 7/3 at 14:15 Comment(0)
L
-1

It working 100% in safari..i tried

@media screen and (-webkit-min-device-pixel-ratio:0) 
{
::i-block-chrome, Class Name {your styles}
}
Lustihood answered 29/9, 2017 at 7:41 Comment(1)
This works on older versions of Safari, not current ones-- 6.1 and newer.Albertinaalbertine
B
-1

I have tested and it worked for me

@media only screen and (-webkit-min-device-pixel-ratio: 1) {
 ::i-block-chrome, .myClass {
    height: 1070px !important;
  }
}
Builtup answered 16/1, 2019 at 7:12 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.