Merge pull request #1 from bpd01001/css-questions-browser-specific-st…

…yling initial commit: vendor prefixes
bpd01001 · Apr 11, 2019 · fe2fdbd · fe2fdbd
2 parents 72d5147 + d8c6b9a
commit fe2fdbd
Show file tree

Hide file tree

Showing 2 changed files with 25 additions and 0 deletions.
diff --git a/.DS_Store b/.DS_Store
diff --git a/03 - CSS/how-would-you-approach-fixing-browser-specific-styling-issues.md b/03 - CSS/how-would-you-approach-fixing-browser-specific-styling-issues.md
@@ -0,0 +1,25 @@
+To approach browser specific styling issues, vendor or browser prefixes should be applied to the front of certain styling properties. This will allow browsers to use certain styling features that aren't yet fully supported by all browsers in a standard.
+
+Here are all the CSS browser prefixes:
+Android:
+    -webkit-
+Chrome:
+    -webkit-
+Firefox:
+    -moz-
+Internet Explorer:
+    -ms-
+iOS:
+    -webkit-
+Opera:
+    -o-
+Safari:
+    -webkit-
+
+If including a vendor prefix for a property, all vender prefixed versions should be included first before the standalone property:
+-webkit-transition: all 4s ease;
+-moz-transition: all 4s ease;
+-ms-transition: all 4s ease;
+-o-transition: all 4s ease;
+transition: all 4s ease;
+