Bug 14516 - Dropbox mode barcode input has odd coloring (alert class css)
Summary: Dropbox mode barcode input has odd coloring (alert class css)
Status: RESOLVED DUPLICATE of bug 20959
Alias: None
Product: Koha
Classification: Unclassified
Component: Templates (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Owen Leonard
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-09 19:56 UTC by Nick Clemens (kidclamp)
Modified: 2019-04-03 09:42 UTC (History)
6 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Picture of colored barcode input (128.87 KB, image/png)
2015-07-09 19:56 UTC, Nick Clemens (kidclamp)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Clemens (kidclamp) 2015-07-09 19:56:55 UTC
Created attachment 40901 [details]
Picture of colored barcode input

When dropbox mode is checked the barcode input box changes color (see attached screenshot)  This coloring is unusual and makes the barcode input hard to read.  Additionally, once you click anywhere else on the screen the coloring disappears, which is odd too.

To reproduce:
1 - Browse to Circulation->Returns
2 - Check the dropbox mode box
3 - Check in a book or enter an invalid barcode
4 - See the input box change
5 - Click anywhere outside of that box
6 - See the box revert

The relevant styling comes from:
FILE boostrap.min.css:
 .alert,.alert h4{color:#c09853;}

FILE staff-global.css:
input.alert {
         background-color : #FFFF99;
         border-color: #900;
  }

returns.tt has multiple addClass("alert") and removeClass("alert") so I am not sure if this is intentional  or a bug
Comment 1 Jonathan Druart 2015-07-14 16:17:03 UTC
Is it a new behavior?
Comment 2 Katrin Fischer 2019-03-16 11:45:10 UTC
Owen, could you take a look here maybe?
Comment 3 Owen Leonard 2019-03-18 18:45:20 UTC
This would be fixed by Bug 20959 if anyone is interested in moving that one along
Comment 4 Katrin Fischer 2019-03-18 20:49:55 UTC
We'll just mark it as a duplicate then :)

*** This bug has been marked as a duplicate of bug 20959 ***