Hot answers tagged safari
5
You could use a virtual machine, like Virtualbox, VMware, etc. but you would need to have a license of Mac OS to test it with.
Safari, however, should look the same on all operating systems it runs on (in theory), and that seems like a pretty big flaw, so I would assume that the problem is somewhere else.
4
I tried it and it works perfectly for me. Note that the color and font-size properties won't have any effect in Chrome, since no text gets displayed. (Firefox displays the alt text if the image cannot be found.) Using the width property, for example, shows that it works fine. I'll post my code below for you to see.
However, to your original question, ...
4
You should probably just use src="//ajax.googleapis.com/..." which is a good way to allow this to work in both http and https pages.
Serving http assets in a page served via https will raise warnings in most browsers, while serving https assets in http pages usually is okay but might be "slower" because of the cryptology overhead.
4
Assuming that Safari on Mac is showing favicons for other websites (try any stackexchange website), you probably need to clear the browser cache.
Also, try adding a random number (using JS or Server-script like PHP) to your favicon reference, like below:
EDIT- Also, add type attribute and try again? (see below)
<!-- FAVICON -->
<link
...
3
I don't think I've ever seen an official listing of versions, so you'll have to piece things together a little.
For your immediate question, there's a page in the Safari Web Content Guide that uses the 3.2 UserAgent string as an example, and gives it as "Mozilla/5.0 (iPad; U; CPU OS 3_2 like Mac OS X; en-us) AppleWebKit/531.21.10 (KHTML, like Gecko) ...
3
There are certainly differences. Looking at just the rendering front, Safari and Chrome will inevitably use different versions of Webkit (it's development is pretty fast-moving). Any differences are likely to be minor, though.
Besides rendering, there is also Javascript to think about and minor things like font differences and platform differences (Safari ...
3
I have solved the situation by doing URL ReWriting with the following rule:
RewriteRule (/res/)(.*)/(.*)/(.*)/(.*) /Magic94Scripts/mgrqispi94.dll?APPNAME=$2&PRGNAME=ViewResource&ResID=$3&size=$4 [I,O,U]
And using URLs such as:
/res/FileManager/2785/9/TheVideo.mp4
Crazy, but it now works. I can only assume quicktime now only inspects the URL ...
2
As the attribute selector is defined in the W3C CSS spec, you should be able to use it. But browsers implementations vary, and are more or less reliable.
As you can see on SitePoint Reference support for CSS attribute selector, Webkit's support is buggy. You could also see that IE's css attribute selector support varies from one version to another.
Thus ...
2
If it's local development why not just add additional JS code at the beginning of your GATC script, like an alert('GATC fired'); ?
Or: See this discussion on monitoring HTTP traffic on serverfault. Some of the mentioned tools are available on both Windows and Linux.
1
I can't seem to find anything either about this, but the one thing I can assume is that because the mobile screen is much smaller that the scroll speed is probably faster, e.g. if you do a big long swipe on the mobile vs a swipe on the desktop it wouldn't scroll as fast because there is less data to scroll.
1
Regarding information about such things in general, the Unicode standard is authoritative in matters of character codes. But it does not prescribe the use of characters. Various sources need to be consulted; in matters of mathematical and physical notations, you can consult the ISO 80000 series of standards (available from standards organizations for rather ...
1
You're looking for a list of unicode characters and an explanation of how to use them. Unicode characters should work in any browser regardless of platform.
The ℏ is written as ℏ and ℎ as ℎ in a html document.
If you're representing complex equations you might get on better with LATEX
1
This is a known problem of Safari on Windows.
http://www.the-art-of-web.com/system/safari-http-auth/
Considering the fact that Basic authentication is a historical relic these days, you can stop using it and switch to a form based authentication instead.
Or there are Apache modules which allows you to set up cookies on client side just by using Basic ...
1
Had a look around and found this question over at SO, and some other threads apparantly this is a header problem
Their suggested solution is as follows "images which contain the "content-length" header randomly disapper, removing this at the server side solves this bug..."
Download livehttp headers and see if you can confirm this content-length header is ...
1
YES, there are differencies. Minor ones? It depends.
Whem I 1st tested an iPad in the shop under my house I looked at some of my websites. I had a select box in a form that was not working on Safari on iPad.
Tested back in office on a PC: it did work on Chrome, but it did not work on Safari!
And since in the specific case the select box was a mandatory ...
1
One to remember is the difference in Mac's rendering of fonts, and that seems to be at it's most extreme in Safari.
I just took these screenshots on my Mac, and you can see that Safari renders the line a bit bigger. Over lots of text, this can have a significant effect on the size of divs.
I don't have Windows to hand, so if somebody else could post a ...
1
The biggest difference I have noticed is with form elements such as dropdowns and input boxes.
These can be manipulated easily on Windows Safari (e.g. padding, rounded corners, line-height) but Mac Safari does not adhere to much of this CSS on it's forms.
I've also noticed further differences between 'desktop' Safari and mobile Safari - i.e. in an iPad.
...
1
It is caused by Safari's behaviour and can be avoided by using JavaScript to disable context menus:
var browser = navigator.userAgent;
if (browser.toLowerCase().indexOf('safari') > 0)
{
var allLinks = document.body.getElementsByTagName('a');
for (var i=0; i<allLinks.length; i++) {
allLinks[i].oncontextmenu = function() { return false ...
1
Modern browsers are automatically decode URLs before displaying on the location bar, but internally still using the real address which will include two different encodings for the path to the resource and the domain.
When you copy the location from the browser it copy the original address with a purpose to make sure that it would act as a web address when ...
1
It's unclear exactly what you're asking about; it seems you're confusing concepts of encryption, content encoding, and URL encoding.
I'll assume this is not related to encryption. Regarding content encoding, any modern browser (even IE 6) handles Unicode. As long as your PHP files are encoded as UTF-8 or UTF-16, you should be able to use any Hebrew ...
1
Not sure if this will help but was speaking with someone this morning who mentioned that GoDaddy chain there SSL certificates and that some bits of software don't trust this as they can not look further down the chain.
this article talks about the issue: SSLShopper cert not trusted
Only top voted, non community-wiki answers of a minimum length are eligible
