Support from Acquia helps fund testing for Drupal Acquia logo

Comments

DeaOm created an issue. See original summary.

DeaOm’s picture

Assigned: DeaOm » Unassigned
Status: Active » Needs review
FileSize
62.93 KB

Status: Needs review » Needs work

The last submitted patch, 2: coding_standards-3005007-2.patch, failed testing. View results

DeaOm’s picture

Fixed most of the CSS problems, the backgorund image one still remains, because it needs to be added as it's own class, so there is no repeating of the image, which is not allowed. But there was no twig template, so I hope everything still works after CSS changes. Needs review and work.

HongPong’s picture

Title: Fix coding standards » Fix CSS coding standards

Missing semicolon here on the background attribute. Also I believe this should be a background-image attribute if there is no positioning or size included.

	+.admin-menu .dropdown .admin-menu-toolbar-category > active-trail {
   text-shadow: #333 0 1px 0;
-  background: url(toolbar.png) 0 0 repeat-x;
+  background: url(toolbar.png)
Neslee Canil Pinto’s picture

Status: Needs work » Needs review
FileSize
553 bytes

Coding Standards added

Status: Needs review » Needs work

The last submitted patch, 6: fix-css-coding-standard-standard-3005007-6.patch, failed testing. View results

Neslee Canil Pinto’s picture

Neslee Canil Pinto’s picture

Status: Needs work » Needs review

Status: Needs review » Needs work

The last submitted patch, 8: fix-css-coding-standard-3005007-8.patch, failed testing. View results

Neslee Canil Pinto’s picture

Status: Needs work » Needs review
FileSize
16.01 KB

Updated Coding Standard

Status: Needs review » Needs work

The last submitted patch, 11: fix-css-coding-standard-3005007-11.patch, failed testing. View results

Neslee Canil Pinto’s picture

Status: Needs work » Needs review
FileSize
16 KB

Updated Coding Standard

Status: Needs review » Needs work

The last submitted patch, 13: fix-css-coding-standard-3005007-13.patch, failed testing. View results

Neslee Canil Pinto’s picture

Status: Needs work » Needs review
FileSize
16 KB

Updated Coding Standard

Status: Needs review » Needs work

The last submitted patch, 15: fix-css-coding-standard-3005007-15.patch, failed testing. View results

Neslee Canil Pinto’s picture

Status: Needs work » Needs review
FileSize
16.01 KB

Updated Coding Standard

Status: Needs review » Needs work

The last submitted patch, 17: fix-css-coding-standard-3005007-17.patch, failed testing. View results

Neslee Canil Pinto’s picture

Status: Needs work » Needs review
FileSize
16.01 KB

Updated Coding Standard

Status: Needs review » Needs work

The last submitted patch, 19: fix-css-coding-standard-3005007-19.patch, failed testing. View results

Neslee Canil Pinto’s picture

Status: Needs work » Needs review
FileSize
15.92 KB

Updated Coding Standard

Status: Needs review » Needs work

The last submitted patch, 21: fix-css-coding-standard-3005007-21.patch, failed testing. View results

Neslee Canil Pinto’s picture

Status: Needs work » Needs review
FileSize
212.88 KB

Fixed all coding standard issues. Build Showing Test Failed

HongPong’s picture

This cleanup looks good to me. @Neslee Canil Pinto keep in mind that "failed testing" results right now are to be expected since the test framework code has not been revised much if at all yet. The only problem you should be concerned about is if the patch doesn't apply, I believe. (also in most cases the test frameworks here are not aware of CSS in general)

Neslee Canil Pinto’s picture

Ok @HongPong
So Further how should I proceed

HongPong’s picture

These all appear to be the correct changes to me in this case. I have not tested this patch but it covers: replacing ID with class; capitalization; removing !important tags (yes!). This brings us much closer to correct CSS. So with the point we are at now, I think it should be committed, but we should get another opinion for more certainty.

Also in the future we need to be aware, as you covered in this patch, that there are multiple CSS files to keep track of on this module (we have seen other patches that did not cover some of them).

I think we could approve this and move onto #2490318: Administration Menu Javascript ESLint errors to cover the Javascript equivalent/similar code style issues. All of this helps because then we won't get tons of confusing code smell warnings, moving into the trickier issues later. Thanks again!!

Neslee Canil Pinto’s picture

HongPong’s picture

@Neslee if I can get a little time I will test it today and if it's solid I will commit it.

Neslee Canil Pinto’s picture

Ok @HongPong take your time👍

thalles’s picture

Replacing # admin-menu by .admin-menu would not break any menu?

pifagor’s picture

Status: Needs review » Needs work

Replacing # admin-menu by .admin-menu would not break any menu?

In my opinion, this should not be done.

thalles’s picture

Category: Task » Support request
Status: Needs work » Fixed

This module has been deprecated for Drupal 8.
For Drupal 8: the Admin Toolbar provides an experience similar to admin_menu with the core toolbar.

Thanks @all!

Status: Fixed » Closed (fixed)

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