search vs. institutional search placeholder text not visible in IE8
|Assignee:||José Raddaoui Marín||% Done:|
|Category:||Search / Browse|
|Target version:||Release 2.0.0|
|Google Code Legacy ID:||Tested version:|
I suspect this is a known issue, but it appears that the placeholder attribute of <input> is not supported in IE9 or earlier (I only have IE8 to test) - so it is not obvious until performing a search whether the institutional filter is set.
I'm not sure what your approach is in terms of how backward compatible to be in browser support, but as one example there is a major USask system for which IE9 is still not yet supported.
#1 Updated by Dan Gillean over 8 years ago
- Category set to Search / Browse
- Status changed from New to Duplicate
Tim, please correct me if I've misunderstood, but I think this actually duplicates an issue that you filed a while ago (which still hasn't been fixed - the text is currently not visible in any browser) - issue #5587. Marking duplicate for now.
#2 Updated by Tim Hutchinson over 8 years ago
These are really two different issues, although of course related:
#5587: when you click into the search box, the text next to the radio buttons is not visible in the Dominion theme. This is a CSS issue since it's fine in the AC theme
The new issue is that the placeholder text shown in the search box before you click into it (i.e. "Search" or "Search University of Podunk Archives") is not visible in earlier versions of IE. This is a browser compatibility issue so I assume would need a different solution. Potentially it would be addressed by USask work on #3897, in terms of visual clues to indicate whether your search is scoped to an institution.
So feel free to merge them if that fits better with your approach (since they both relate to the search hox), but it's not the same bug.
#3 Updated by Dan Gillean over 8 years ago
- Status changed from Duplicate to New
- Assignee set to Jesús García Crespo
- Target version set to Release 2.0.0
Ah, thanks for clarifying Tim! I'll keep this issue as is; it's been related to #5587 already so that should let our developers know. If the fixes involved end up being different, we should keep separate issue tickets. Appreciate all your helpful catches!