Closed (fixed)
Project:
Drupal Commons
Component:
Theme
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Feb 2013 at 12:35 UTC
Updated:
1 Mar 2013 at 18:10 UTC
Jump to comment: Most recent file
When the message box appears on the commons origins theme it is overlapped by the search box.
See screenhot attached.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | commons-header.jpg | 17.73 KB | blacklabel_tom |
| #3 | alert-issue.png | 117.59 KB | rosemeria |
| #1 | commons-messages-box-overlapped-origins-theme-1912182.patch | 1.46 KB | blacklabel_tom |
| error-issue.jpg | 29.75 KB | blacklabel_tom |
Comments
Comment #1
blacklabel_tom commentedHeres a patch it adds 20px to the top margin of the messages box seems to do the trick.
I did have a play around with the z-indexing, but it meant that something was always overlapped.
Comment #2
ezra-g commentedComment #3
rosemeria commentedConfirm message box fixed on Feb-14 dev version, but what happened to the white down arrow in the search box. See image...
Comment #4
blacklabel_tom commentedAttached is the header I see, I updated to the latest dev version yesterday morning.
I'll have time to update to todays dev version later and I'll see what it looks like then
Cheers
Tom
Comment #5
autolyst commentedIMHO.. and just a suggestion, as its seems were chasing some element of the search field in a number of issues why not take the dropdown filter out of the search box and place the filter below it like on drupal.org. As making room for it, the search field, and the magnifying icon, all seem to push something around. I feel if something is going to get kicked out of the box anyway why not just specify the one item that seems to be pushing the others arond outside of the box. Its not uncommon to add search facets below the field, in fact its quite common just look at any google search results page, and they have way more space to work with. You could even theme the facet like the text below "whats going on?"
Comment #6
ay13 commentedthis issue seems to be fixed in recent commons_origins updates.