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.
Well-known consequence of BT #4479072: HTMLEditorKit uses always default editor kit for rendering of frames. The basic problem is that NB registers its editor kits using JEditorPane.registerKitForContentType, including "text/html" -> our org.netbeans.modules.editor.html.HTMLKit, but JEditorPane and the Swing kits are not fully prepared for this. Specifically, HTML rendering assumes that the text/html kit is an HTML viewer; not only HTMLEditorKit itself when working with framesets, but also many third-party plugin developers assume this is true as it is in a plain Swing app, and become very confused when HTML source is rendered instead! Possible workaround for the JRE bug on the NB side: cease to use JEditorPane's registration mechanism for registering our editor kits. Sort of an incompatible API change, I think, but probably one we could live with. Just ignore the JEP registration mechanism entirely, and roll our own - probably just using the editor module's existing mechanism: in CloneableEditorSupport.createEditorKit, look up the data object in the system filesystem under Editors/$contenttype/EditorKit (could also use JNDI if core/naming is available) and ask for InstanceCookie (instanceof EditorKit). Precise impact of API change unknown. Probably cannot be made fully compatible.
Do you think that this issue should be fixed for next version?
It would be nice, but I don't know of anything that depends on it.
Nice to have == future. Can be changed if somebody depends on this.
*** Issue 5511 has been marked as a duplicate of this issue. ***
http://openide.netbeans.org/source/browse/openide/src/org/openide/awt/SwingBrowserImpl.java.diff?r1=1.24&r2=1.25 Expecting proposed fix for 4479072
*** Issue 32821 has been marked as a duplicate of this issue. ***
It was fixed for JDK 1.5. Changing this issue to possible ENHANCEMENT untill the JDK is available.
After talk with rkubacki I'm closing as WONTFIX. Any workaround would be quite difficult and it is possible that the JDK bugfix will get into 1.4.2_x.