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 217124 - Broken browser interaction when running project with fresh dir for the first time
Summary: Broken browser interaction when running project with fresh dir for the first ...
Status: RESOLVED DUPLICATE of bug 215459
Alias: None
Product: platform
Classification: Unclassified
Component: Embedded Browser (show other bugs)
Version: 7.2
Hardware: PC Linux
: P2 normal (vote)
Assignee: Stanislav Aubrecht
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-21 07:03 UTC by Vladimir Riha
Modified: 2012-08-21 08:38 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
IDE log (35.13 KB, text/x-log)
2012-08-21 07:03 UTC, Vladimir Riha
Details
screenshot (123.60 KB, image/png)
2012-08-21 07:04 UTC, Vladimir Riha
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Riha 2012-08-21 07:03:25 UTC
Created attachment 123329 [details]
IDE log

To reproduce:
- download Easel zip build and run it with fresh user dir
- open sampleApp.zip from our wiki
- run index.html in embedded browser. Now you are asked for specifying JavaFX dir
- when I do that, the page renders properly but as you can see on the screenshot, DOM Tree window is missing, Selection Mode button in browser's toolbar as well and also zooming combo box is empty and all buttons look disabled. 
- if I close the window and run the file again, it works fine


Product Version: NetBeans IDE Dev (Build EaselCSS-520-on-20120821)
Java: 1.7.0_06; Java HotSpot(TM) Client VM 23.2-b09
System: Linux version 3.2.0-29-generic-pae running on i386; UTF-8; en_US (nb)
JavaFX 2.2.0 b21
Comment 1 Vladimir Riha 2012-08-21 07:04:55 UTC
Created attachment 123330 [details]
screenshot

btw when run in Chrome it works fine so it is related to embedded browser only
Comment 2 Petr Jiricka 2012-08-21 08:38:55 UTC
Duplicate of 215459.

*** This bug has been marked as a duplicate of bug 215459 ***