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.
There are a number of usability issues with the css editor components. Most of them stem from their being separate from the editor: 1. The entire editor is in a scroll pane, rather than putting the contents of the tabbed pane inside the scroll pane. Otherwise you keep having to scroll down, scroll back up to click another tab, scroll down again - a lot of work for nothing. 2. Why are there two TopComponents here? It would make more sense to override creating the editor in the EditorSupport for CSS and embed the CSS editor in the lower half of a split pane and the text editor in the top. 3. Why is the preview a separate TopComponent? Can't figure out when it actually needs to be separately closable - does someone ever *not* want a preview of their CSS?
-->web/css
#1 already fixed #2 more flexible, user can move/change size of the windows freely #3 someone may need just to preview a css file, do not need the editor. The preview should be activated if a node with Previewable cookie is selected.