Page MenuHomePhabricator

CSS issue on Special:ContentTranslation
Open, Needs TriagePublicBUG REPORT

Assigned To
None
Authored By
Juan90264
Jul 25 2021, 7:04 AM
Referenced Files
F34563016: 3.png
Jul 25 2021, 7:04 AM
F34563007: 1.png
Jul 25 2021, 7:04 AM
F34563010: 2.png
Jul 25 2021, 7:04 AM

Description

Hi! I'm reporting a bug that is occurring in Special:ContentTranslation, being a bug precisely in the CSS of the page where we started translating the articles on Wikipedia.

List of steps to reproduce (step by step, including full links if applicable):

What happens?:
For you to better understand the error I made some screenshots at the place where the CSS bug occurs, on Wikipedia in Portuguese:

1.png (529×1 px, 76 KB)

1. As you can see in this first capture, the CSS is working in it.

2.png (560×1 px, 104 KB)

2. In this second capture, as you can see the header is not formatted, I put the red arrows to emphasize this, the header is unformatted when the first capture is formatted.

3.png (843×1 px, 163 KB)

3. Now in this third capture, you can see that the section that follows "== Discovery ==" is unformatted, which used to exist.

What should have happened instead? :

1. In the first capture, we can see how the page should be, while translating the articles or CSS.

Event Timeline

Reedy renamed this task from I found a bug in the CSS for Special:ContentTranslation to CSS issue on Special:ContentTranslation.Jul 25 2021, 10:55 PM

I am not sure I understand the issue correctly. What do you mean by "formatted" in the sentense "the section that follows "== Discovery ==" is unformatted, which used to exist.".

In the first capture, we can see how the page should be, while translating the articles or CSS.

First capture is the dashboard of Translation tool. That is not where translations happen. Could you please try to elaborate? My native language is not English.

My understanding of the issues in case it is helpful:

  • The first issue is that the top header lacks separation at the bottom when in the translation editor (second screenshot). There you can see that the button with the user name has no separation with the formatting tool bar from VE right below. The first screenshot of the dashboard is provided as an example of the expected margin below such the header.
  • The second issue (illustrated in the 3rd screenshot) shows that section titles inside Content Translation editor use a text style that is different from the one you'd see in the article. While the article shows section titles using a serif font with a line below, inside content Translation, they are shown using the default sans-serif font and no line below.