a.contextual-links-trigger:hover,
div.contextual-links-active a.contextual-links-trigger {
  background-position: 2px -18px;
}
div.contextual-links-active a.contextual-links-trigger {
  background-position: 2px -18px;
  background-color: #fff;
  border-color: #ccc;
  border-bottom: none;
  position: relative;
  z-index: 1;
  -moz-border-radius: 4px 4px 0 0;
  -webkit-border-bottom-left-radius: 0;
  -webkit-border-bottom-right-radius: 0;
  border-radius: 4px 4px 0 0;
}

No needs to redefine it.

Files: 
CommentFileSizeAuthor
#1 duplicate-css.patch473 bytesbleen18
PASSED: [[SimpleTest]]: [MySQL] 33,044 pass(es).
[ View ]
context.patch0 bytesdroplet
PASSED: [[SimpleTest]]: [MySQL] 33,060 pass(es).
[ View ]

Comments

StatusFileSize
new473 bytes
PASSED: [[SimpleTest]]: [MySQL] 33,044 pass(es).
[ View ]

The patch in the original post was empt (0k) so I'm using this issue to show someone how to create & submit a patch to D.O.

Here we go.

Status:Needs review» Reviewed & tested by the community

Oh, didn't notice it, sound like drupal.org problem. I seem another 0 byte patch and created an issue #1290674: Don't test 0 bytes patch.

Thank @bleen18. can I mark it RTBC ?

droplet, if you have tested that the patch applies and youve double checked that there are no adverse effects, I think its safe for this to be marked RTBC... generally though the person who writes the patch is not supposed to be the one who marks it RTBC but since technically your patch was never posted... feel free.

Just adding a second +1.

bleen18's patch looks good; I checked this over yesterday but didn't RTBC it due to the 0 byte patch.

FYI, We've got an issue for cleaning up every single module's CSS, with a plan for what we want to do with them here:

http://drupal.org/node/1089868

In the future, if you could please use them that would be great. Thanks.

Not really related to the "global CSS clean-up and separation" effort; looks ready to fly for me.

Version:8.x-dev» 7.x-dev

Committed to 8.x. I'd not spotted this was tagged for backport but it looks fine there too.

Version:7.x-dev» 8.x-dev

@sun Had there already been a patch in that issue, this would be addressed as part of it and there would be duplicate work going on. It's just a note for future reference though... I didn't change the status and agree this is ready.

Version:8.x-dev» 7.x-dev

Status:Reviewed & tested by the community» Fixed

Committed and pushed to 7.x. Thanks!

Automatically closed -- issue fixed for 2 weeks with no activity.