Comments

rudraram’s picture

Language content settings form has no classes in the markup.

<form action="/en/admin/config/regional/content-language" method="post" id="language-content-settings-form" accept-charset="UTF-8">

lewisnyman’s picture

Yeah we should be able to add one

leeotzu’s picture

StatusFileSize
new1.13 KB

Please review the patch.

manjit.singh’s picture

Status: Active » Needs review
rudraram’s picture

StatusFileSize
new111.03 KB

The above patch looks fine but the styles of language.admin.css are getting overwritten by content_translation.admin.css. Screenshot attached.

ss

rudraram’s picture

Status: Needs review » Needs work
lewisnyman’s picture

manjit.singh’s picture

@rudraram #5 Can you specify the URL, where you are tested and screenshots belongs to ?

rudraram’s picture

@Manjit the url is admin/config/regional/content-language

alexpott’s picture

Status: Postponed » Needs work

The blocker has been committed - we can now do this one.

manjit.singh’s picture

Assigned: Unassigned » manjit.singh
manjit.singh’s picture

Assigned: manjit.singh » Unassigned
Status: Needs work » Needs review
StatusFileSize
new452 bytes
new113.61 KB
new114.69 KB

I think we don't need to add class now. Class is added in this issue #2485409: Clean up content translation CSS inline with our CSS standards. And css is already there in content_translation.admin.css. I have removed CSS file (language.admin.css) in patch. Please check screenshot as well.

Check there is no override in CSS

alt

alt

Status: Needs review » Needs work

The last submitted patch, 12: clean-up-language-css-2485439-12.patch, failed testing.

The last submitted patch, 12: clean-up-language-css-2485439-12.patch, failed testing.

rudraram’s picture

@Manjit.Singh I think you should also remove the language.admin.css from the language.libraries.yml file too.

manjit.singh’s picture

yup that's what i was thinking about, can you take this up please

rudraram’s picture

Sure I'll work on this.

rudraram’s picture

Status: Needs work » Needs review
StatusFileSize
new891 bytes
new439 bytes

Removed language.admin.css from the language.libraries.yml. Attaching patch and interdiff,

rudraram’s picture

Now we need some screenshots on this. @Manjit can you add some screenshots just like you did in #12

manjit.singh’s picture

Assigned: Unassigned » manjit.singh
manjit.singh’s picture

StatusFileSize
new69.48 KB
new68.94 KB

@rudraram there is some minor difference in the table. Please check the screenshots.

Before
alt

After
alt

manjit.singh’s picture

Assigned: manjit.singh » Unassigned
Status: Needs review » Needs work
rudraram’s picture

@manjit are you talking about the size of the "content type" column?

Sorry I'm not able to exactly see the difference. It would be very helpful if you could mark the difference.

manjit.singh’s picture

StatusFileSize
new497.55 KB

@rudraram check table differences in screencast :)

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

hog’s picture

Status: Needs work » Needs review
StatusFileSize
new891 bytes
new1 KB

Re-rolled patch.
No regressions now for me.

andypost’s picture

Status: Needs review » Reviewed & tested by the community

I think that small visual diff (#21 #24) is fine

alexpott’s picture

Status: Reviewed & tested by the community » Needs work

We don't remove CSS like this - the core promise is to move these things to Stable so theme's extending form classy and stable don't change but core's markup and css can improve.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

hoemmawelt’s picture

StatusFileSize
new488.79 KB

I'm a little bit confused - deleting the width on both classes will break the layout of the entire table. The length of content values will than determine table row width.

tstoeckler’s picture

Issue summary: View changes
Status: Needs work » Closed (works as designed)

Yup, that sounds reasonable to me. Closing. Please re-open if there is anything to do here.