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 221158 - Selected rule in CSS Styles|Document not always propagated to Rule Editor
Summary: Selected rule in CSS Styles|Document not always propagated to Rule Editor
Status: RESOLVED FIXED
Alias: None
Product: web
Classification: Unclassified
Component: CSS Visual Tools (show other bugs)
Version: 7.3
Hardware: PC Linux
: P3 normal (vote)
Assignee: Marek Fukala
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2012-10-31 10:21 UTC by Vladimir Riha
Modified: 2012-11-01 13:48 UTC (History)
1 user (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 Vladimir Riha 2012-10-31 10:21:01 UTC 
I haven't found any pattern or steps to reproduce, but sometimes after "many" modifications of css via Rule Editor and CSS Styles with a running HTML page in Chrome, if I switch to Document view, then Rule Editor is not populated by simple clicking on a rule in CSS Styles. If I double click on it, it works. Sometimes it seems that it is "locked" to caret position so that's why double click helps and why it repopulate the rule editor.




Product Version: NetBeans IDE Dev (Build web-main-9047-on-20121031)
Java: 1.7.0_10-ea; Java HotSpot(TM) Client VM 23.6-b04
Runtime: Java(TM) SE Runtime Environment 1.7.0_10-ea-b11
System: Linux version 3.2.0-31-generic-pae running on i386; UTF-8; en_US (nb
Comment 1 Marek Fukala 2012-11-01 13:45:36 UTC 
I believe 

changeset:   237871:468d3c9ce8a5
summary:     fixing livecycle of the CssStylesPanelProviders' component;
propagating the panel's lookups to the CssStyles TopComponent

Please reopen if you encounter it on the latest builds. It would be also handy if you run the ide with the -J-Drule.editor.level=FINE switch so I can possibly figure out what happened. If you face the issue withe the log enabled, please kill the ide immediately so I can identify the part of the log where the issue happened.

Thanks.
Comment 2 Vladimir Riha 2012-11-01 13:48:07 UTC 
Thanks, I'll try it.