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.
In the past few weeks only, I have on several occasions encountered a problem changing component in Issuezilla. I add some comments to a bug, then change the Component field, leaving the Subcomponent field untouched, and submit. I next get a page informing me that the existing Subcomponent does not exist in the new Component and that I need to select a new one; this is normal and expected. I select a new Subcomponent from among the choices and submit again. Then I get a curious page saying "A legal component was not set. This may indicate a bug in your browser." Now 1. A legal component *was* set, of course - if it is referring to the Component field, of course I picked an offering from the drop-down list on the first page, and if to the Subcomponent field, then I picked an offering from the choices on the second page. And naturally the Component and Subcomponent I pick are commonly used components with at least hundreds of bugs in them. 2. What bug in my browser, exactly? I am using Firefox 1.5.0.8. Which is a recent, popular, well-supported browser. 3. I cannot even reproduce this problem consistently. I just got this error on http://www.netbeans.org/issues/show_bug.cgi?id=65959 after trying to add a comment and change comp/subcomp to ide/ui from editor/options. (There is no ide/options.) So I pressed Back twice, reset the Component to the original value (editor), leaving Subcomp at options and leaving my Comments intact, and submitted, to preserve my comments. Then I clicked on the link to return to the page, again changed Component to ide, submitted, on request changed Subcomponent to ui, and submitted, and this time it worked fine (no error page).
Collab, perhaps something to do with the CRM connector ? Ref issue 90217.
In issue #91105 I am now getting a "Page Not Found" error when I try to change component from apisupport/project -> core/ui. It seems that it works as expected if and only if I make no other changes to the issue at a time besides adjusting the component. If I try to also add a component / edit summary / adjust keywords at the same time, then there is an error.
I got ""A legal component was not set. ..." again from issue #91619. Any progress on this bug? Unless something strange has changed in my browser configuration, this seems like a recent regression.
If you look at the http://www.netbeans.org/issues/editparams.cgi parameters for "browserissuemessage" there has been a message set which is "This may indicate a bug in your browser" message where this will be displayed when IZ gets unexpected data from the browser based on the "strictvaluechecks"[Do stricter integrity checking on both form submission values and values read in from the database"]. I am trying to reproduce to see what was bad data has been sent by the browser. I think this is something to do with the data captured by the browser. Still debugging.
*** Issue 91692 has been marked as a duplicate of this issue. ***
Seems to me the issues [issue 91150, issue 90965, issue 81075 and issue 90676] are related with each other. Still looking into it.
I just got this when updating issue 92065. I had changed component, then was asked to change version, target milestone and subcomponent. After doing so I see "issie processed, and "A legal Component was not set; This may indicate a bug in your browser." None of my changes, including the comment I added and the cc I added, appeared. I was able to make my changes in 2 seperate commits - first the comment and cc, then I went back and changed the component.
I checked the internal issue tracking system and found that there's an issue filed for this but in that issue report this problem seemed to be happening when trying to associate an issue with an 'imported' component. IZ allows to import issues from one project to another. However, here we have a single DB set up. I am not sure what could be causing this. Jack, can you please check how the component (the one to which you tried to associate an issue) was created? Meanwhile, I will research on this further.
> Jack, can you please check how the component (the one to which you tried to > associate an issue) was created? I tried to assign it to www. I have no idea how that component was created, I imagine by SourceCast itself, or Collab staff, in ~06/2000. Unless it was created "new" during the last SC upgrade, or imported from the previous version ? I just got this again for issue 92385, where I tried to change component from www -> ide. I don't know how the ide component was created, but my bet is just added via the standard IZ admin interface. cc'ing Jan, who was at one time IZ admin and maybe created that component. Jan, can you comment ?
It seems I can't change component at the same time as I add a comment. If I do those changes in 2 seperate steps (first add comment, commit, then go back and change component), it works. See issue 92065 and issue 92385 for examples of this.
Sorry, Jack, I have no idea how the 'ide' component was created. I don't think I created it, but it has been around for years, so I don't really remember.
Jack, Jan Can we use the 'ide' subcomponent for testing? Thanks Padma
Please do not test in the 'ide' component. You can use some bogus component like 'smoketest'.
Hi, We tested using a 'test' component using the firefox/IE and found the issue as non-consistent. Can you verify from your end to see this still exists or not . Regards, Kavitha Support Operations
I have not personally seen this happen in a while. However it was never reproducible that I know of, so there is no obvious way to verify that it is gone.
Jack, I see this case as non-replicable even from our end to verify. Do you think anyother way for reproducing this? Your thoughts? Regards, Kavitha Support Operations
marked as resolved by mistake
As Jesse says, no obvious way to verify if this is fixed. I haven't seen it in a while. I have a vague recollection that there was a fix in patch 10 that may have addressed this ?
Jack, Found this issue as fixed and non-replicable now. Can we close it? Regards, Kavitha Support Operations
I guess so, hasn't been seen in a while. Any comment on my last question ? > I have a vague recollection that there was a fix in patch 10 that may have addressed this ?
Jack, referring the url - http://www.collab.net/rn/3_5_1_10.html. Patch 10 notes talks about other fixes and not for this non-reproducible issue. Regards, Kavitha Support operations
OK. Closing, though it seems clear noone is sure it is really fixed, it just hasn't been seen in a while. Thanks.
This seems to be back. It was reported about 1hr after the patch 11/config change/server restart this morning, perhaps that is related.
*** Issue 121208 has been marked as a duplicate of this issue. ***
Let me explain the issue #121208. It complains about special NetCAT bug form [1] that does something behind the scenes. This form contains one visible field 'component_tmp' (drop down menu) and hidden field 'component' with default value "". The reason for this is to simplify the selection of correct component by providing human friendly descriptions and doing the mapping behind the scenes. The case described in #121208 should work though: <form METHOD="POST" ACTION="http://www.netbeans.org/issues/post_bug.cgi" NAME="simpleform" onSubmit="return validate_form()"> <script language="javascript"> ... function validate_form() { var validated=true; if ((document.simpleform.component_tmp.selectedIndex == 0) && (validated)) { alert('Please choose a component for this issue.'); validated=false; } ... if (validated) { ... if (document.simpleform.component_tmp.value=='editor_code') { document.simpleform.component.value='editor'; } ... return validated; } ... document.write('<input type=hidden name="component" value="">\n'); ... document.write('<p><b>Choose Component :</b> \ <SELECT NAME="component_tmp">\ ... <OPTION VALUE="editor_code">Source Editor</option>\ </select>'); ... </script> </form> [1] http://qa.netbeans.org/processes/cat/60/bug_form.html
Started to work on the issue , will update you on the findings. Ramya Support Operations
Created attachment 52603 [details] Step 1: screenshot of the filled out bug form with debug message
Created attachment 52604 [details] Step 2: Screenshot of the result from post_bug.cgi script.
I added some debug message to be sure that both 'component' and 'subcomponent' are set correctly before exiting 'validate_form()' function: ... alert("User selected: " + document.simpleform.component_tmp.value + "\nAssigned component: " + document.simpleform.component.value + "\nAssigned subcomponent: " + document.simpleform.subcomponent.value + "\nValidated:" + validated); return validated; } This was added to http://qa.netbeans.org/processes/cat/60/test.html testing bug submission form.
I have finally found what is the cause of this. Project admins of 'editor' project decided 2 days ago to rename all subcomponents and this is the result. Thus I am closing this issue again and apologize for wasting your time.
We recently moved out from Collabnet's infrastructure