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.
Product Version = NetBeans IDE 7.3.1 (Build 201304162201) Operating System = Windows XP version 5.1 running on x86 Java; VM; Vendor = 1.7.0_21 Runtime = Java HotSpot(TM) Client VM 23.21-b01 I created a new JavaFx Hello World project and I have tested running in browser. Clicking on the "Project Properties - Set Configuration - Run_in_Browser" does not take effect, running the application with this setting, still results to desktop mode running(standalone).
This is not true at JavaFx FXML applications
This error appears every time when I change the default borwser from Netbeans menu - Tools-Options - for ex. to chrome, and after then trying to set the configuration from <default_config> to Run_in_Browser in Project Properties right click and Set config.
Created attachment 134667 [details] Javafx Proiect properties settings Here, in the picture below, the "Manage" button, does not work as i would expected. I mean choosing a browser with "Manage" button does not take its effect, still remains the pre-chosen Chrome browser
Honza is on vacation. Petr G, can you follow up?
(In reply to comment #4) > Honza is on vacation. Petr G, can you follow up? Incorrect issue ... sorry
I am unable to duplicate this error with NB 7.3.1 or 7.4 20130902 I can switch browsers with no problem - (although I'm having trouble getting Firefox to run it)
(In reply to mr_lou_d from comment #6) > I am unable to duplicate this error with NB 7.3.1 or 7.4 20130902 > I can switch browsers with no problem - > (although I'm having trouble getting Firefox to run it) Thanks for verification, I'm also unable to reproduce the issue. Regarding Firefox 23: it had a bug (https://bugzilla.mozilla.org/show_bug.cgi?id=902375) lehel: Please make sure that you have in configuration combobox in toolbar selected correct configuration (and in project's settings correct behavior for that configuration). If the issue will persist on the latest dev build (and clean userdir), please reopen with updated/more detailed information how to reproduce the issue.