Show delete button in input[type=search] only if the field is editable and focused/hovered.

Source/core/css/html.css

 /*
  * The default style sheet used to render HTML.
  *
  * Copyright (C) 2000 Lars Knoll (knoll@kde.org)
  * Copyright (C) 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011 Apple Inc. All rights reserved.
  *
  * This library is free software; you can redistribute it and/or
  * modify it under the terms of the GNU Library General Public
  * License as published by the Free Software Foundation; either
  * version 2 of the License, or (at your option) any later version.
@@ skipping 438 matching lines @@
     -webkit-user-modify: read-only !important;
     -webkit-margin-start: 2px;
 }
 
 input[type="search"]::-webkit-search-cancel-button {
     -webkit-appearance: searchfield-cancel-button;
     display: block;
     flex: none;
     -webkit-user-modify: read-only !important;
     -webkit-margin-start: 1px;
+    opacity: 0;

[keishi, 2013/12/09 06:24:49]

I think this should be "visibility: hidden". "opacity: 0" will still receive
events so I  would guess that tapping a blank area in the text field (on a touch
screen) might clear the value unintentionally.

[tkent, 2013/12/09 06:45:18]

Oh, touch devices..  You're right.

We don't have this issue with mice.
As for touch device, we shouldn't hide buttons at all because of
discoverability. What do you think?

+}
+
+input[type="search"]:enabled:read-write:-webkit-any(:focus,:hover)::-webkit-search-cancel-button {
+    opacity: 1;
 }
 
 input[type="search"]::-webkit-search-decoration {
     -webkit-appearance: searchfield-decoration;
     display: block;
     flex: none;
     -webkit-user-modify: read-only !important;
     -webkit-align-self: flex-start;
     margin: auto 0;
 }
@@ skipping 655 matching lines @@
 @page {
     /* FIXME: Define the right default values for page properties. */
     size: auto;
     margin: auto;
     padding: 0px;
     border-width: 0px;
 }
 
 /* noscript is handled internally, as it depends on settings. */