X-Git-Url: http://git.ithinksw.org/extjs.git/blobdiff_plain/3789b528d8dd8aad4558e38e22d775bcab1cbd36..6746dc89c47ed01b165cc1152533605f97eb8e8d:/docs/resources/themes/stylesheets/ext4/default/widgets/form/_file.scss

diff --git a/docs/resources/themes/stylesheets/ext4/default/widgets/form/_file.scss b/docs/resources/themes/stylesheets/ext4/default/widgets/form/_file.scss
deleted file mode 100644
index 3f83ea20..00000000
--- a/docs/resources/themes/stylesheets/ext4/default/widgets/form/_file.scss
+++ /dev/null
@@ -1,32 +0,0 @@
-@mixin extjs-form-file {
-
-    .#{$prefix}form-file-wrap {
-        .#{$prefix}form-text {
-            color: #777;
-        }
-
-        .#{$prefix}form-file-btn {
-            overflow: hidden;
-            float: left;
-        }
-
-        .#{$prefix}form-file-input {
-            position: absolute;
-            top: -4px;
-            right: -2px;
-            height: $form-field-height + 8;
-            @include opacity(0);
-
-            /* Yes, there's actually a good reason for this...
-             * If the configured buttonText is set to something longer than the default,
-             * then it will quickly exceed the width of the hidden file input's "Browse..."
-             * button, so part of the custom button's clickable area will be covered by
-             * the hidden file input's text box instead. This results in a text-selection
-             * mouse cursor over that part of the button, at least in Firefox, which is
-             * confusing to a user. Giving the hidden file input a huge font-size makes
-             * the native button part very large so it will cover the whole clickable area.
-             */
-            font-size: 100px;
-        }
-    }
-}
\ No newline at end of file