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.

Bug 118175 - I18N - java doc not show in IEbrowser if another javadoc is showing
Summary: I18N - java doc not show in IEbrowser if another javadoc is showing
Status: RESOLVED WORKSFORME
Alias: None
Product: ide
Classification: Unclassified
Component: Extbrowser (show other bugs)
Version: 6.x
Hardware: Sun All
: P3 blocker (vote)
Assignee: issues@ide
URL:
Keywords: I18N
Depends on:
Blocks: 120529
  Show dependency tree
 
Reported: 2007-10-09 03:10 UTC by Ken Frank
Modified: 2008-03-26 17:18 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ken Frank 2007-10-09 03:10:24 UTC
not sure if this is locale specific.

when using IE browser on xp, in ja locale, when there is browser open,
and if its showing another javadoc from another project (or maybe if its just open showing any page),
generate javadoc again on another project - the javadoc for that project is not shown.

I have changed the tab browsing behavior to show in same tab, new tab or new window but results are the same.

firefox does not show this.

perhaps there is some config situation of IE I need to do ?
Comment 1 Ken Frank 2007-10-09 03:36:24 UTC
even if another IE window present, or a new tab on same window, the problem exists.

ken.frank@sun.com
Comment 2 Jan Pokorsky 2007-10-09 14:49:50 UTC
The javadoc module uses API org.openide.awt.HtmlBrowser to show URL. The impl delegating to IE resides in extbrowser.
Reassigning.
Comment 3 Ken Frank 2007-10-09 15:31:19 UTC
I see this also when generate uml report; I don't know if it happens for things like
running web app or other things that cause nb to invoke a browser -- is it common code
that is used or does each project implement its own ?

ken.frank@sun.com
Comment 4 David Konecny 2007-10-31 13:24:55 UTC
I cannot reproduce it - works just fine for me. Could you please try it on western locale to confirm that it is just ja
locale issue? Looking into code there is no difference between handling of IE and FF. Thanks, David.
Comment 5 David Konecny 2007-10-31 13:33:34 UTC
Actually when generated Javadoc is shown in IE the IE's information bar is shown and says "To help protect your
security, Internet Explorer has restricted this file from showing active content that could access your computer. Click
here for options...". So perhaps it is IE who is preventing you from opening the Javadoc. I can click "Allow" in
information bar and it disappears for ever. Could you check your IE's security settings and tweak it to see whether it
has an impact on this issue or not? (I'm not IE user)
Comment 6 Ken Frank 2007-10-31 19:14:19 UTC
its very strange.  I did reduce security setting but no affect; sometimes the popup
appears sometimes not.

but what I discover (though see no exceptions in log)

1. no ie open - project with mbyte in name = mbyte in path to it
ie opens generated javadoc ok.

2. ie open - project without mbyte in path, generate javadoc and it shows in IE

a. then gen javadoc for project with mbyte in path - it does not show 
(even though it did show  in #1)
 
b. gen javadoc for another project that does not have mbyte in path, and it too
show

c. so its just project with mbyte in path that does not show


ken.frank@sun.com
Comment 7 Ken Frank 2008-01-10 19:47:11 UTC
based on last comments, this does seem to be i18n kind of issue
related to use of multibyte -
can this be committed to be fixed for 6.1 ?

ken.frank@sun.com
Comment 8 David Konecny 2008-01-14 07:31:45 UTC
Re. "committed to be fixed for 6.1" - no. I do not have environment to reproduce this - XP with JA locale. And on EN
locale it worked fine. From code perspective there is no difference in starting IE or FF so my suspicion is it is IE
issue. I can try to reproduce it on Vista as time permits.
Comment 9 Ch Nguyen 2008-03-26 17:18:36 UTC
This might be similar to issue 128033 which has been fixed. Can you verify?