Problem
1. Enable Locale module.
2. Add a couple languages.
3. Go to the interface translation screen.
4. Enter one translation string.
5. *All of them* will be marked as changed.
This is due to the locale table getting the changed class and the row also getting it.
Proposal
The selector for the changed class should be more specific.
Comment | File | Size | Author |
---|---|---|---|
#12 | no-indentation.png | 59.68 KB | RainbowArray |
#12 | td-column.png | 83.25 KB | RainbowArray |
#11 | pre-patch-all-changed.png | 42.62 KB | RainbowArray |
#11 | post-patch-one-changed.png | 40.79 KB | RainbowArray |
#9 | interface-translation-changed-hover-2049387-9.patch | 375 bytes | RainbowArray |
Comments
Comment #1
Gábor HojtsyComment #2
LewisNymanComment #3
YesCT CreditAttribution: YesCT commentedtagging front end so it shows on the multilingual hub front page when people are looking for tasks matching their skills.
Comment #4
RainbowArrayI'm trying to help review this issue, but I'm running into problems in duplicating this issue.
Sorry if it is silly that I can't get this to work. I stopped by the Drupal core mentoring office hours and was shown this issue as an option to tackle. I did review the patch in #1986400: Table style update. At first glance, I didn't see anything that should trigger a problem with checkboxes, but it's hard to test without enabling the modules.
If you can point me in the right direction, I'd be glad to take another look!
Comment #5
Gábor HojtsyIndeed. The locale module is called the interface translation module on the user interface. Then you can configure languages under Configuration > Regional and Language > Languages. See the blue "add language" button on that page at the top.
Hope this helps. Thanks for looking into this issue.
Comment #6
RainbowArrayFor the locale changed bug, I'm not sure that the patch listed caused the bug. However, the culprit appears to be the following lines in locale.admin.css
Both the table and the row have the class changed applied to them, so the CSS should probably be rewritten as:
One other somewhat unrelated note. If with the new style guide we are getting rid of zebra striping on tables, do we really need odd and even classes on each table row?
Comment #7
RainbowArrayFor the content translation bug, I don't see any CSS lines being applied to the column-settings class (or the field-settings class) on the table row for the image field columns, which is why there's no indentation.
Is this specific to content translation? I don't see anything specifically tied to that module, so I wonder if this is a more general issue with table styles.
Again, I don't see any connection between this bug and the table style update patch.
Comment #8
RainbowArrayComment #9
RainbowArrayHere's a patch to fix the user interface bug. Now only the row color should change, rather than the whole table.
Comment #10
RainbowArrayComment #11
RainbowArrayTested the patch, appears to do the trick.
Screenshots, or it didn't happen.
Before:
After:
Comment #12
RainbowArrayHere's a screenshot of the duplication of part two of this issue, where there's no indentation for image items.
When you inspect element on one of the items, like alt, you can see that the table row has the class of column-settings, and the table cell has a class of column.
However, as far I can see there are no special styles being applied to the column-setting or column classes that would create any indentation.
So for there to be indentation, there needs to be some styles to create that indentation.
Is this a problem specific to Locale? Are there other tables that have similar indentation that we could use as a model to determine what sort of indentation should be applied here? Or if there is a generic class that can provide indentation that could be added?
Comment #13
Gábor Hojtsy#1807692: Introduce a column synchronization capability and use it to translate alt and titles through the image field widget added the image field feature. It did these changes to introduce the column indent:
I looked at the blame log for the file but this is still there: http://drupalcode.org/project/drupal.git/blob/refs/heads/8.x:/core/modul...
So either the form ID changed or the table structure changed or there are conflicting rules that apply.
Comment #14
RainbowArrayHmm. I don't see a translation_entity module in the version of 8.x I have downloaded, and I'm pretty sure I'm on the latest version. Is that a contributed module?
Comment #15
RainbowArrayI've learned that the cause of the second error is that when the content translation module was renamed, the CSS filename was not renamed, and the module info file calls the wrong file. I've created a bug report on this and will be uploading a patch there.
#2059719: Content translation admin CSS file not renamed from translation_entity.admin.css
Comment #16
Gábor HojtsyNow needed to retitle this issue since you broke out the fix for one of the problems. This fix looks good too.
Comment #17
Gábor HojtsyComment #18
Gábor HojtsyTagging as quick fix too.
Comment #19
webchickThanks for the before/after screenshots in #11. Very helpful!
Committed and pushed to 8.x. Thanks!
Comment #20
Gábor HojtsyWoot, thanks!
Comment #21.0
(not verified) CreditAttribution: commentedUpdate for current scope