search

mantlik / swingbox-javahelp-viewer

Netbeans plugin which installs alternative javahelp viewer into Netbeans RCP application
GNU Lesser General Public License v3.0
3 stars 1 forks source link

Font style becomes fuzzy for some sections of the help pages #3

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. install plugin and launch help > help content > Search 
2. Typed Swing on the search box and got results
3. Opened several pages and most of them had display font format issues as in 
the attached screenshot

What is the expected output? What do you see instead?
The expected output is correct rendered text which is the case for the normal 
help doc before installing the plugin

What version of the product are you using? On what operating system?
Product Version: NetBeans IDE 7.2.1 (Build 201210100934)
Java: 1.7.0_09; Java HotSpot(TM) 64-Bit Server VM 23.5-b02
System: Mac OS X version 10.7.5 running on x86_64; US-ASCII; en_US (nb)
User directory: /Users/carlosqt/Library/Application Support/NetBeans/7.2.1
Cache directory: /Users/carlosqt/Library/Caches/NetBeans/7.2.1

Please provide any additional information below.

Original issue reported on code.google.com by carlo...@gmail.com on 12 Jan 2013 at 2:10

Attachments:

GoogleCodeExporter commented 8 years ago 
Dear carlosqt,

thank you for the report. 

The presented sample looks like a double rendering effect of the font with 
different font settings for unordered list items text. There were significant 
upstream code changes in the newest version (1.0.2) which is newer than the 
version at the Netbeans Plugin Portal (1.0.1). 

It is not clear from your report whether you installed version from the Plugin 
portal or the version downloaded from the code.google.com. In case your test 
was done with the Plugin Portal version only (1.0.1), could you, please, check 
whether the problem persists in the 1.0.2 version and report your observation 
here?

Original comment by mantl...@gmail.com on 12 Jan 2013 at 7:30

GoogleCodeExporter commented 8 years ago 
hi there,

i tested using the version from the plugin portal page.

i will check if version 1.0.2 works fine.

Original comment by carlo...@gmail.com on 12 Jan 2013 at 7:55

GoogleCodeExporter commented 8 years ago 
Hi again,

I tested version 1.2.0 and I get the same formatting issue with the
difference that now the screen becomes unresponsive and need to Force Quit
to close it... could it be a problem related to Mac OSX?

Carlos

2013/1/12 Carlos Quintanilla <carlosqt@gmail.com>

Original comment by carlo...@gmail.com on 12 Jan 2013 at 8:08

GoogleCodeExporter commented 8 years ago 
Hi Carlos,

thank you very much for your fast response. Unfortunately, I do not have access 
to any Mac OSX computer, so it is difficult for me to diagnose/test the 
problem. As you can see from my attachement below, rendering of the same page 
at the Windows computer does not suffer from the reported problem. 

Nevertheless, your screenshot suggests an option of possible double rendering 
of list items which could be a algorithm problem. I will try to find the source 
of the problem myself or report the problem upstream to the Swingbox/CSSbox 
authors.

As soon as the source of the problem will be discovered, may I take a liberty 
to ask you to test the plugin again before it will be published to check 
whether the problem was fixed?

Original comment by mantl...@gmail.com on 12 Jan 2013 at 9:02

GoogleCodeExporter commented 8 years ago

Original comment by mantl...@gmail.com on 12 Jan 2013 at 9:49

Attachments:

GoogleCodeExporter commented 8 years ago 
This issue was updated by revision aa4eb0cc1f20.

Fix merge of upstream changes

Original comment by mantl...@gmail.com on 10 Feb 2013 at 8:06

GoogleCodeExporter commented 8 years ago 
Carlos,

can you, please, download Build 284 from here: 
http://code.google.com/p/swingbox-javahelp-viewer/downloads/list and check 
whether the problem was fixed on your Mac OSX?

In addition, problem mentioned in your Comment 3 was moved to the Issue 4 and 
fixed as well, I believe. Please feel free to report your feedback/comments to 
the Issue 4.

Original comment by mantl...@gmail.com on 10 Feb 2013 at 8:23

GoogleCodeExporter commented 8 years ago

Original comment by mantl...@gmail.com on 15 Feb 2013 at 12:38