Differences between Safari for Windows and Safari for Mac

1,695

Solution 1

As far as rendering and JavaScript are concerned, there is no difference. What is different is underlaying UI library used for browser itself, but page render is the same.

Solution 2

Font rendering can be different between Mac and Windows Safari as the systems typically have different fonts. As long as your page can gracefully handle missing fonts or different font sizes it should be fine.

Solution 3

Style sheet rendering is significantly different between Safari and Windows. To see this, try creating a page that has an element with a z-index of -1. The windows version will function without issue, the Mac version will not allow you to select the elements. Trust me, I wasted about three hours trying to figure out by trial and error why a page would work in one system but not the other. The worst bit is that when Safari doesn't render something properly, it does so without any indication. You have to debug line for line, a dreadful experience.

Solution 4

I am currently experiencing an issue where floating images in a blog with text wrapping around the image do not properly pad themselves in OS X; works fine in windows. Basically I've added padding to make the image align flush left or right such that the edge of the image is at the same offset as the edge of the text of the post; on OS X the image sticks out past the edge of the text.

Solution 5

I have also seen problems in Safari for Windows that don't exist in Safari for Mac on CSS heavy websites. Can't remember the specifics, but they were there.

Share:
1,695

Related videos on Youtube

Nikhil vyas
Author by

Nikhil vyas

Updated on November 07, 2020

Comments

  • Nikhil vyas
    Nikhil vyas over 3 years

    I have started learning hadoop recently and I am getting the below error while creating new folder -

    vm4learning@vm4learning:~/Installations/hadoop-1.2.1/bin$ ./hadoop fs -mkdir helloworld Warning: $HADOOP_HOME is deprecated. 15/06/14 19:46:35 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:9000. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)

    Request you to help.below are the namdenode logs -

    015-06-14 22:01:08,158 INFO org.apache.hadoop.hdfs.server.common.Storage: Storage directory /home/vm4learning/Installations/hadoop-1.2.1/data/dfs/name does not exist 2015-06-14 22:01:08,161 ERROR org.apache.hadoop.hdfs.server.namenode.FSNamesystem: FSNamesystem initialization failed. org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /home/vm4learning/Installations/hadoop-1.2.1/data/dfs/name is in an inconsistent state: storage directory does not exist or is not accessible. at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:304) at org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirectory.java:104) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:427) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.(FSNamesystem.java:395) at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:299) at org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:569) at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1479) at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1488) 2015-06-14 22:01:08,182 ERROR org.apache.hadoop.hdfs.server.namenode.NameNode: org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /home/vm4learning/Installations/hadoop-1.2.1/data/dfs/name is in an inconsistent state: storage directory does not exist or is not accessible. at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:304) at org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirectory.java:104) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:427) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.(FSNamesystem.java:395) at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:299) at org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:569) at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1479) at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1488)

    2015-06-14 22:01:08,185 INFO org.apache.hadoop.hdfs.server.namenode.NameNode: SHUTDOWN_MSG: /************************************************************ SHUTDOWN_MSG: Shutting down NameNode at vm4learning/192.168.1.102 ************************************************************/

    • Nikhil vyas
      Nikhil vyas almost 9 years
      mkdir: Call to localhost/127.0.0.1:9000 failed on connection exception: java.net.ConnectException: Connection refused
    • chomp
      chomp almost 9 years
      Execute jps in console and update your question with that information please.
    • Nikhil vyas
      Nikhil vyas almost 9 years
      JPS gave the below result -8980 Jps 8129 JobTracker 7914 DataNode 8269 TaskTracker 8052 SecondaryNameNode
    • Nikhil vyas
      Nikhil vyas almost 9 years
      Seems that the name node is missing - not sure why - i did format it and then start-all.sh succefully , but while creating a new directory i get the error as shown in my original question.
    • chomp
      chomp almost 9 years
      Add namenode logs please.
    • Nikhil vyas
      Nikhil vyas almost 9 years
      logs added in the main section
  • FeifanZ
    FeifanZ about 13 years
    Actually, Apple's ported their font rendering engine to Windows. So even the font rendering is the same.
  • David
    David almost 12 years
    Hmm...this got downvoted? Maybe not really an answer, but it has helpful comment/insight. If that's what others thought, then should have added comment that this should have been submitted as a comment (where possible/applicable).
  • Nikhil vyas
    Nikhil vyas almost 9 years
    It worked - thanks a lot - Could you explain me why were these changes required and what exactly happened - thanks again
  • chomp
    chomp almost 9 years
    Your HDFS folders are created on top of your FS. That's why, when i see that your namenode was complaining about those inexistent FS directories (the default ones used to create the hadoop filesystem) i suppose that you didn't create them yet. I tell you to specify those properties in hdfs-site because if you don't do that, it could lead to another problems too. Np
  • chomp
    chomp almost 9 years
    Hope that's enough for you. And maybe you could accept my answer for this question if you have some time ;)