<blink>

Source/WebCore/css/html.css

Index: Source/WebCore/css/html.css
diff --git a/Source/WebCore/css/html.css b/Source/WebCore/css/html.css
index dcb2ca10a1b74cdbb9c29955e1d4afb89d14523c..970b04ea622c329e4acfca192082bd3610f1107e 100644
--- a/Source/WebCore/css/html.css
+++ b/Source/WebCore/css/html.css
@@ -1193,6 +1193,18 @@ nobr {
     white-space: nowrap
 }
 
+@-webkit-keyframes blink {
+    from { opacity: 1.0; }
+    to { opacity: 0.0; }
+}
+
+blink {
+  -webkit-animation-name: blink;
+  -webkit-animation-iteration-count: infinite;
+  -webkit-animation-timing-function: cubic-bezier(1.0,0,0,1.0);
+  -webkit-animation-duration: 1s;

[Mike West, 2013/04/05 16:44:07]

1s seems arbitrary. What do other browsers do here?

[M-A Ruel, 2013/04/05 16:49:52]

It's the right value.

" The United States Federal Government's Section 508 states that pages should
avoid causing the screen to flicker with a frequency between 2 Hz and 55 Hz, a
range which covers rapidly blinking text. This does not seem to apply to blink
element itself, which blinks at frequency of 1 Hz. "

Reference: http://en.wikipedia.org/wiki/Blink_element

[Avi (use Gerrit), 2013/04/05 22:00:07]

According to Wikipedia, "In Mozilla Firefox the text alternates between being
visible for three quarters of a second and being invisible for one quarter of a
second."

It's clear to me that we should follow their lead. The danger I see here is that
site owners may have designed their sites for that blink frequency (say, by
coordinating it with animated GIFs), and we run the risk of incompatibility if
we don't mimic them well.

+}
+
 /* states */
 
 :focus {