Closed (works as designed)
Project:
Drupal core
Version:
8.6.x-dev
Component:
language.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
8 May 2015 at 10:23 UTC
Updated:
26 Jan 2019 at 12:56 UTC
Jump to comment: Most recent, Most recent file

Comments
Comment #1
rudraram commentedLanguage 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">Comment #2
lewisnymanYeah we should be able to add one
Comment #3
leeotzu commentedPlease review the patch.
Comment #4
manjit.singhComment #5
rudraram commentedThe above patch looks fine but the styles of language.admin.css are getting overwritten by content_translation.admin.css. Screenshot attached.
Comment #6
rudraram commentedComment #7
lewisnymanOk then, postponing on #2485409: Clean up content translation CSS inline with our CSS standards
Comment #8
manjit.singh@rudraram #5 Can you specify the URL, where you are tested and screenshots belongs to ?
Comment #9
rudraram commented@Manjit the url is admin/config/regional/content-language
Comment #10
alexpottThe blocker has been committed - we can now do this one.
Comment #11
manjit.singhComment #12
manjit.singhI 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
Comment #15
rudraram commented@Manjit.Singh I think you should also remove the language.admin.css from the language.libraries.yml file too.
Comment #16
manjit.singhyup that's what i was thinking about, can you take this up please
Comment #17
rudraram commentedSure I'll work on this.
Comment #18
rudraram commentedRemoved language.admin.css from the language.libraries.yml. Attaching patch and interdiff,
Comment #19
rudraram commentedNow we need some screenshots on this. @Manjit can you add some screenshots just like you did in #12
Comment #20
manjit.singhComment #21
manjit.singh@rudraram there is some minor difference in the table. Please check the screenshots.
Before

After

Comment #22
manjit.singhComment #23
rudraram commented@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.
Comment #24
manjit.singh@rudraram check table differences in screencast :)
Comment #26
hog commentedRe-rolled patch.
No regressions now for me.
Comment #27
andypostI think that small visual diff (#21 #24) is fine
Comment #28
alexpottWe 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.
Comment #34
hoemmawelt commentedI'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.
Comment #35
tstoecklerYup, that sounds reasonable to me. Closing. Please re-open if there is anything to do here.