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 11281 - Node actions do not make sense on Web Browser objects
Summary: Node actions do not make sense on Web Browser objects
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: All All
: P4 blocker (vote)
Assignee: _ rkubacki
URL:
Keywords:
Depends on: 16198
Blocks:
  Show dependency tree
 
Reported: 2001-04-11 01:02 UTC by Jason Rush
Modified: 2008-12-22 17:36 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Rush 2001-04-11 01:02:57 UTC 
In the Options window, the objects under "Web Browsers" (i.e. ICE Browser, 
External Browser (Windows), etc. ) have actions such as Delete, Cut and Copy 
which do not make sense for these objects.

First, delete should not be enabled for these objects because if the user 
deletes "ICE Browser" or "External Browser (Windows/Unix)", those objects 
cannot be restored.  Only "External Browser (Command-Line)" can be restored 
after deletion.

Second, using copy and paste actions on these objects does not work as 
expected.  If you copy the ICE Browser node and paste it, it creates a second 
instance of the ICE Browser, but when you edit the second instance it modifies 
the first as well.

Since these actions do not make sense on these nodes, they should be disabled.
Comment 1 _ rkubacki 2001-04-12 13:16:28 UTC 
This is a couple of issues:

1) It has sense to create FilterNode that will redefine behaviour of 'Web
Browser' node so that it will create children with only required actions.

2) all instances  of Ice Browser shares one settings - I will create separate bug
Comment 2 _ rkubacki 2001-04-24 10:13:22 UTC 
Nodes representing browsers are created in core.
Comment 3 Jan Chalupa 2001-05-05 20:35:49 UTC 
Target milestone -> 3.3
Comment 4 _ rkubacki 2001-10-12 10:26:18 UTC 
The second problem is solved. The first one persists.

Vita, can you check if this can be solved? Is there anything what I
can do in my module to declare that the browser is not deletable? At
least it would be nice to guarantee that SwingBrowser cannot be deleted.
Comment 5 Vitezslav Stejskal 2001-10-12 12:14:12 UTC 
There is already an issue #16198, which will add support for (un)deletable settings in 
the XML layers. I have marked this issue to depend on #16198.
Comment 6 Jan Chalupa 2001-11-27 11:50:54 UTC 
Target milestone -> 3.3.1.
Comment 7 Jan Chalupa 2001-11-27 11:54:28 UTC 
Target milestone -> 3.3.1.
Comment 8 Jan Chalupa 2002-01-11 14:04:42 UTC 
Target milestone -> 3.4
Comment 9 Jan Chalupa 2002-01-11 14:08:32 UTC 
Target milestone -> 3.4
Comment 10 Jan Chalupa 2002-01-11 14:09:25 UTC 
Target milestone -> 3.4
Comment 11 Jan Chalupa 2002-01-11 14:11:58 UTC 
Target milestone -> 3.4
Comment 12 _ rkubacki 2002-03-22 09:17:40 UTC 
Postponing due to dependency on issue 16198
Comment 13 Alexei Mokeev 2002-05-28 09:20:33 UTC 
Looks like second problem appears again.
For example: If you'll copy External Browser(Command Line) node and 
paste them, then changes in one node will be reflected in all copied 
nodes.
So looks like all copies are just point to one object.
(Checked on FFJ4.0 rc5 under all OS's)
Comment 14 _ rkubacki 2002-05-28 09:59:02 UTC 
-
Comment 15 _ rkubacki 2002-05-28 10:06:23 UTC 
The first part is tracked by issue 24123. We should create new issue
for sharing settings in command line browser. OTOH it works correctly
in NB3.4 and problem with icebrowser was fixed too so I mark it as fixed.
Comment 16 Alexei Mokeev 2002-05-28 10:48:39 UTC 
Ok. Copy work well in trunk(for SWING browser and for command line 
browser)
Comment 17 Quality Engineering 2003-07-01 15:47:24 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verified
Comment 18 Quality Engineering 2003-07-01 16:50:17 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.