Closed (fixed)
Project:
Flux
Version:
7.x-1.x-dev
Component:
Code
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Jan 2013 at 00:17 UTC
Updated:
17 Mar 2013 at 11:10 UTC
Jump to comment: Most recent file
minor css issue
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | flux-contextual_links-1885682-13.patch | 2.1 KB | discipolo |
| #3 | finaloutput.jpg | 251.65 KB | discipolo |
Comments
Comment #1
discipolo commentedor is this fixed already in dev?
Comment #2
zirafa commentedPlease provide a screenshot with more details about this problem so I can debug.
Comment #3
discipolo commentedHere is a Screenshot.
Comment #4
zirafa commentedHm, looks like maybe a padding issue. Does this error occur with certain contextual links or all contextual links (panels, views, blocks) etc)? It could be that the Pushtape admin links at the top don't have enough space to support contextual links for "configure block".
Comment #5
discipolo commentedcontextual links in the menu will be fixed if we change every occurrence of
#block-menu-menu-pushtape ul to #block-menu-menu-pushtape ul.menu" and #block-menu-menu-pushtape a to #block-menu-menu-pushtape .menu in the css files, to make sure we are not styling the contextual links. you get the point.
the contextual links for views also act strangely. caused by style.css line 229 making #main display inline. removing inline makes the contextual links appear in the right place.
Comment #6
discipolo commentedif you need a patch feel free to assign as task to me.
Comment #7
zirafa commentedHm, shouldn't have to change the class name itself - it seems more likely a CSS bug.
Comment #8
zirafa commentedHave a patch for this? It could also lead to fixing the original issue too.
Comment #9
discipolo commentedboth things need to be fixed. the second issue is the position of the contextual links "launcher", the other issue is the contextual links themselves.
will make a patch for both if you change status to task and assign to me.
Comment #10
zirafa commentedIMO it is a bug, not a task, see: http://drupal.org/node/73179. Since we are just dealing with Drupal markup, I still believe the issue should/can be fixed via CSS.
You can assign to yourself if you have a patch to submit, thanks.
Comment #11
discipolo commentedThe task at Hand is writing the patch since the issue is identified. I already specified the required css changes that will resolve the bug. Changing the class selector in the css file will make sure we are not theming contextual links along with the other menus by accident. I am not proposing anything other than css changes .
Comment #12
zirafa commentedOk, I misunderstood your comment in #5. Thought you were suggesting markup changes, but understand the issue now. I'll try and find some time to review the fix in #5.
In the future, submitting a patch will make it easier to review proposed changes & avoid confusion.
Please read the post I linked to, which helps explain task vs bug report. It's not a hard and fast rule, but generally there is no need to switch the Category of the issue midway through - the Status is usually used for that.
From Tips for making a good issue report:
Comment #13
discipolo commentedhere is the promised patch with the changes from #5
Comment #14
zirafa commentedCommitted to 7.x-1.x