Elements cut-off in preferences dialog for nl locale

RESOLVED INVALID

Status

Mozilla Localizations
nl / Dutch
RESOLVED INVALID
6 years ago
6 years ago

People

(Reporter: whimboo, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [mozmill-l10n], URL)

(Reporter)

Description

6 years ago
Our Mozmill l10n tests have been shown that there are some elements which are cut-off due to the localization. The results of the test you can find here:

http://mozmill-ci.blargon7.com/#/l10n/report/ee284dfa9d664754a65676abbc01a595

Details:

 Node is cut off by 0 px at the left: prefpane#SignonViewerDialogPane. Parent node: deck[flex=1][anonid=paneDeck]
Node is cut off by 4 px at the bottom: tab#generalTab. Parent node: tabs#tabsElement
Node is cut off by 4 px at the bottom: tab#networkTab. Parent node: tabs#tabsElement
Node is cut off by 4 px at the bottom: tab#updateTab. Parent node: tabs#tabsElement
Node is cut off by 4 px at the bottom: tab#encryptionTab. Parent node: tabs#tabsElement
Node is cut off by 4 px at the bottom: tab#ca_tab. Parent node: tabs#certMgrTabbox
Is there something changed in the preferences because it is strange that is is suddenly cuff off.

and how do i fix a report about 0 px?
i wil have a look on my linux setup tonight.
(Reporter)

Comment 3

6 years ago
Tim, we have started those tests on Friday. So a lot of locales are affected because we never did those type of testing before.

I'm currently not sure about the 0px message. It could be a bug in our test but we will figure that out over on bug 614579.
Are you sure your test are ok? i am looking at the preferences and there is nothing cut off. every windows looks ok.

Mozilla/5.0 (X11; Linux i686 on x86_64; rv:15.0) Gecko/20120611 Thunderbird/15.0a2, new profile
(Reporter)

Comment 5

6 years ago
So as it turned out yesterday the test gives a false positive for the tabs in the advanced section too. That means we have disabled the crop tests again on bug 741301 and will wait with re-enabling those until all of the known issues have been solved. Sorry for the noise.

In the meantime lets close this bug as invalid.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.