Bug 1231441 - Unable to read the text of the buttons of the security dialogue.
Summary: Unable to read the text of the buttons of the security dialogue.
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: icedtea-web
Version: 21
Hardware: All
OS: All
high
low
Target Milestone: ---
Assignee: jiri vanek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-13 12:05 UTC by Frank Büttner
Modified: 2015-06-25 08:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-25 08:56:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Picture of the web start security dialogue. (27.99 KB, image/png)
2015-06-13 12:05 UTC, Frank Büttner
no flags Details

Description Frank Büttner 2015-06-13 12:05:06 UTC
Created attachment 1038249 [details]
Picture of the web start security dialogue.

Description of problem:
When an security question is shown on German, than the "No" (Nein) button is not readable. The "Yes" (Ja) button is readable.

Version-Release number of selected component (if applicable):
icedtea-web-1.6-1.fc21.x86_64

How reproducible:
every time

Steps to Reproduce:
1. open an web start application on an German system.

Actual results:
An security dialogue is only parable readable.

Expected results:
The dialogue shut be complete readable.

Additional info:
Sample for it: The skat game from http://www.skat-online.com/

Comment 1 jiri vanek 2015-06-17 14:22:48 UTC
Ok, right.I dont know why the buttons do not adapt, but ytou are right. Most of  the buttons "longer then three texts" on most of the dialogs are really affected.

Will try to fix it soon.
Sorry!

Comment 2 jiri vanek 2015-06-24 09:54:44 UTC
posted upstream.
http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2015-June/032584.html

It should be pushed soon and should reach  next release.

Comment 3 jiri vanek 2015-06-25 08:56:31 UTC
pushe dto head, 1.6 and 1.5.


Note You need to log in before you can comment on or make changes to this bug.