This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
see 118174 on j2se - all the info and gifs are there and it happens for mobility project also. I realize some multibyte not surpposed to be used as to wtk limitations, but some mbyte can be ok to use and that is where this problem could occur and user would noto be able to navigate to the javadoc sections.
corrected summary - problem is not in generating but in viewing on firefox. ken.frank@sun.com
fixed Checking in javadoc; /cvs/mobility/project/src/org/netbeans/modules/mobility/project/ui/resources/buildscript/javadoc,v <-- javadoc new revision: 1.4; previous revision: 1.3
reopening - the problem still happens. am using euc project encoding for the project, and as before on solaris in ja locale and with path to project that has mbyte, although project name does not new project using utf-8 project encoding - same problem changing browser encoding to euc-jp does not help (its in utf-8 now) ken.frank@sun.com
The original issue was about generating Javadoc and it is now generating correctly with encoding information in the headers so it is correctly detected in my browser. When I change the encoding, save the file again and regenerate Javadoc everything works with the new encoding and everything is correctly displayed in my browser (SeaMonkey). I am sorry but I cannot fix you browser. Closing as works for me.
this issue, like the one it referred to was about firefox, which is, as far as I know, a supported nb browser and is one of the ones listed in the options of nb. I can see from other related issues, that its not going to be fixed so can see that it wont be fixed here, but I don't think the reason for closing it - that it works with some other browser, is a valid one since this was about firefox. ken.frank@sun.com
From the related issue I don't see anything. The only mentioned issue #118174 is closed as fixed, this issue is fixed exactly the same way and the fix is working for me. If you know about some other issues, please fill another issue with detailed description. BTW SeaMonkey (former Mozilla) is based on the same rendering engine as Firefox.
Created attachment 56904 [details] Hidden input in Create Key Pair dialog (GTK)